{"answers":{"affected":"2 open source packages ship an affected version, including mantisbt/mantisbt.","exploited":"There is no known exploitation of CVE-2026-40596 in the wild and no public exploit code.","fix":"Upgrade mantisbt/mantisbt to 2.28.2 or later.","what":"CVE-2026-40596 is a high-severity cross-site scripting vulnerability in mantisbt, published on 22 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-40596 and fix it if it is affected.\n\nWhat it is: CVE-2026-40596 is a high-severity cross-site scripting vulnerability in mantisbt, published on 22 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-40596 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mantisbt/mantisbt (Packagist): affected from 2.11.0; fixed in 2.28.2\n- mantisbt/mantisbt (Packagist): affected from 2.11.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-40596/ (Markdown: https://insights.sbomify.com/CVE-2026-40596/index.md)","id":"CVE-2026-40596","markdown":"https://insights.sbomify.com/CVE-2026-40596/index.md","name":"CVE-2026-40596","record":{"aliases":["GHSA-j3v9-553h-x28j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Issue tracking software","requires_auth":"low_privilege","summary":"Authenticated users can inject HTML via font settings, leading to reflected XSS and potential account takeover in MantisBT.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:L/VA:L/SC:H/SI:H/SA:L","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. Versions 2.11.0 through 2.28.1 allow any authenticated user to inject arbitrary HTML by updating their account's font family. Upon exploitation, an XSS payload would be reflected on every MantisBT page. Leveraging another vulnerability (CSP bypass, see GHSA-9c3j-xm6v-j7j3), the attacker could achieve account takeover. This issue has been fixed in version 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 is vulnerable to XSS and potential account takeover via user font family preference update","id":"CVE-2026-40596","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"MantisBT has a Content Security Policy bypass via attachments","id":"CVE-2026-40597"},"packages":[{"ecosystem":"Packagist","fixed":["2.28.2"],"introduced":["2.11.0"],"last_affected":[],"package":"mantisbt/mantisbt","purl":null,"source":"GHSA-j3v9-553h-x28j"},{"ecosystem":"Packagist","fixed":["2.28.2"],"introduced":["2.11.0"],"last_affected":[],"package":"mantisbt/mantisbt","purl":"pkg:composer/mantisbt/mantisbt","source":"GHSA-j3v9-553h-x28j"}],"prev":{"headline":"Chartbrew: Incorrect Access Control in public chart and export routes via missing onReport and SharePolicy checks","id":"CVE-2026-40595"},"products":["mantisbt"],"published":"2026-05-22","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-22","vendors":["mantisbt"]},"summary":"Authenticated users can inject HTML via font settings, leading to reflected XSS and potential account takeover in MantisBT.","url":"https://insights.sbomify.com/CVE-2026-40596/"}