Summary
OpenSTAManager has HTML Injection in modules/utenti/edit.php
An HTML Injection vulnerability exists in the user group creation functionality that allows an attacker to inject arbitrary HTML content into the application interface.
The vulnerability occurs when user-supplied input in the group name field is not properly sanitized before being rendered, allowing an attacker to inject HTML elements such as anchor tags. This may enable phishing attacks or unintended redirection when other users interact with the injected content.
Details
The vulnerable code responsible for rendering this content is located in: modules/utenti/edit.php
<i class="fa fa-users mr-2"></i>'.tr('Utenti del gruppo: _GROUP_', [
'_GROUP_' => '<span class="text-primary">'.$group->getTranslation('title').'</span>
PoC
A malicious user can inject HTML content into the Name field when creating a new user group.
After selecting the group, the application renders the injected HTML without proper sanitization. As a result, the anchor tag is displayed as an active link in the interface.
The injected anchor tag is also visible when the group is assigned to a user.
When a user clicks the injected link, the browser redirects them to the attacker-controlled URL.
Impact
This vulnerability is an HTML Injection caused by improper sanitization of user-supplied input before rendering it in the application interface. Any user who views the interface where the injected content is rendered may be impacted.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2026-44701 has a CVSS score of 3.5 (Low). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.11-beta); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-44701? CVE-2026-44701 is a low-severity cross-site scripting (XSS) vulnerability in devcode-it/openstamanager (composer), affecting versions <= 2.10.1. It is fixed in 2.11-beta. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2026-44701? CVE-2026-44701 has a CVSS score of 3.5 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of devcode-it/openstamanager are affected by CVE-2026-44701? devcode-it/openstamanager (composer) versions <= 2.10.1 is affected.
- Is there a fix for CVE-2026-44701? Yes. CVE-2026-44701 is fixed in 2.11-beta. Upgrade to this version or later.
- Is CVE-2026-44701 exploitable, and should I be worried? Whether CVE-2026-44701 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-44701 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-44701? Upgrade
devcode-it/openstamanagerto 2.11-beta or later.