CVE-2026-41897

CVE-2026-41897 is a medium-severity cross-site scripting (XSS) vulnerability in mantisbt/mantisbt (composer), affecting versions >= 1.0.0, < 2.28.2. It is fixed in 2.28.2.

Summary

Lack of validation of filter_target parameter on return_dynamic_filters.php (normally used as an AJAX in View Issues Page) allows an attacker to inject arbitrary HTML if the target is a TEXTAREA custom field.

Workarounds

None

Credits

Thanks to siunam (Tang Cheuk Hei) 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.

Affected versions

mantisbt/mantisbt (>= 1.0.0, < 2.28.2)

Security releases

mantisbt/mantisbt → 2.28.2 (composer)

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.

See it in your environment

Remediation advice

  • c885af13f0b8596714ffe11df757c09f35fbd8f4

Frequently Asked Questions

  1. What is CVE-2026-41897? CVE-2026-41897 is a medium-severity cross-site scripting (XSS) vulnerability in mantisbt/mantisbt (composer), affecting versions >= 1.0.0, < 2.28.2. 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.
  2. Which versions of mantisbt/mantisbt are affected by CVE-2026-41897? mantisbt/mantisbt (composer) versions >= 1.0.0, < 2.28.2 is affected.
  3. Is there a fix for CVE-2026-41897? Yes. CVE-2026-41897 is fixed in 2.28.2. Upgrade to this version or later.
  4. Is CVE-2026-41897 exploitable, and should I be worried? Whether CVE-2026-41897 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
  5. What actually determines whether CVE-2026-41897 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.
  6. How do I fix CVE-2026-41897? Upgrade mantisbt/mantisbt to 2.28.2 or later.

Other vulnerabilities in mantisbt/mantisbt

CVE-2026-44657CVE-2026-44655CVE-2026-42071CVE-2026-42070CVE-2026-41897

Stop the waste.
Protect your environment with Kodem.