Summary
Improper escaping of tag names retrieved from History in Timeline (my_view_page.php) allows an attacker to inject HTML and, if CSP settings permit, achieve execution of arbitrary JavaScript, when displaying a tag that has been renamed or deleted.
Workarounds
- Edit offending History entries (using SQL)
- Wrap
$this->tag_namein a string_html_specialchars() call in IssueTagTimelineEvent::html()
Credits
MantisBT thanks Vishal Shukla for discovering and responsibly reporting the issue.
Impact
Cross-site scripting (XSS).
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-33548 has a CVSS score of 6.1 (High). The vector is network-reachable, no 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.28.2); 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.
Remediation advice
f32787c14d4518476fe7f05f992dbfe6eaccd815
Frequently Asked Questions
- What is CVE-2026-33548? CVE-2026-33548 is a high-severity cross-site scripting (XSS) vulnerability in mantisbt/mantisbt (composer), affecting versions = 2.28.0. It is fixed in 2.28.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2026-33548? CVE-2026-33548 has a CVSS score of 6.1 (High). 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 mantisbt/mantisbt are affected by CVE-2026-33548? mantisbt/mantisbt (composer) versions = 2.28.0 is affected.
- Is there a fix for CVE-2026-33548? Yes. CVE-2026-33548 is fixed in 2.28.2. Upgrade to this version or later.
- Is CVE-2026-33548 exploitable, and should I be worried? Whether CVE-2026-33548 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-33548 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-33548? Upgrade
mantisbt/mantisbtto 2.28.2 or later.