CVE-2026-33517
HTML/JS injection in MantisBT 2.28.0 tag_delete confirmation.
Is CVE-2026-33517 being exploited?
Not confirmed. CVE-2026-33517 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-33517?
CVE-2026-33517 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-33517?
Yes. A fix has been recorded for CVE-2026-33517. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-33517 affect?
CVE-2026-33517 affects MantisBT 2.28.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-33517?
Upgrade to 2.28.1; or apply workaround to remove the placeholder.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
XSS via tag_delete confirmation; attacker can execute JS in a user's browser if CSP allows, risking session data.
Patch when possible
- affected= 2.28.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.