{"answers":{"affected":"2 open source packages ship an affected version, including mantisbt/mantisbt.","exploited":"There is no known exploitation of CVE-2026-41897 in the wild and no public exploit code.","fix":"Upgrade mantisbt/mantisbt to 2.28.2 or later.","what":"CVE-2026-41897 is a medium-severity cross-site scripting vulnerability in mantisbt, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41897 and fix it if it is affected.\n\nWhat it is: CVE-2026-41897 is a medium-severity cross-site scripting vulnerability in mantisbt, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-41897 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mantisbt/mantisbt (Packagist): affected from 1.0.0; fixed in 2.28.2\n- mantisbt/mantisbt (Packagist): affected from 1.0.0; fixed in 2.28.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41897/ (Markdown: https://insights.sbomify.com/CVE-2026-41897/index.md)","id":"CVE-2026-41897","markdown":"https://insights.sbomify.com/CVE-2026-41897/index.md","name":"CVE-2026-41897","record":{"aliases":["GHSA-j7v9-f46r-2rp4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Issue tracking software","requires_auth":"low_privilege","summary":"Attackers can inject arbitrary HTML via the filter_target parameter in MantisBT, potentially leading to session hijacking or malicious script execution.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Mantis Bug Tracker (MantisBT) is an open source issue tracker. From 1.0.0 to 2.28.1, 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. This vulnerability is fixed in 2.28.2.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"MantisBT: Reflected XSS in Rendering Dynamic Custom Textarea Field","id":"CVE-2026-41897","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"rust-openssl: Unchecked callback length in PSK/cookie trampolines leaks adjacent memory to peer","id":"CVE-2026-41898"},"packages":[{"ecosystem":"Packagist","fixed":["2.28.2"],"introduced":["1.0.0"],"last_affected":[],"package":"mantisbt/mantisbt","purl":null,"source":"GHSA-j7v9-f46r-2rp4"},{"ecosystem":"Packagist","fixed":["2.28.2"],"introduced":["1.0.0"],"last_affected":[],"package":"mantisbt/mantisbt","purl":"pkg:composer/mantisbt/mantisbt","source":"GHSA-j7v9-f46r-2rp4"}],"prev":{"headline":"Coolify: Unauthenticated Deployment Trigger via Webhook HMAC Bypass with Null Secret","id":"CVE-2026-41896"},"products":["mantisbt"],"published":"2026-05-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-30","vendors":["mantisbt"]},"summary":"Attackers can inject arbitrary HTML via the filter_target parameter in MantisBT, potentially leading to session hijacking or malicious script execution.","url":"https://insights.sbomify.com/CVE-2026-41897/"}