Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-73vx-49mv-v8w5

MEDIUM

MantisBT has Stored HTML Injection/XSS when displaying Tags in Timeline

Also known asCVE-2026-33548
Published
Mar 25, 2026
Updated
Mar 25, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk9th percentile+0.15%
0.00%0.23%0.46%0.70%0.0%0.0%0.0%0.2%Apr 26Jun 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
🐘mantisbt/mantisbt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Impact

Cross-site scripting (XSS).

Patches

f32787c14d4518476fe7f05f992dbfe6eaccd815

Workarounds

  • Edit offending History entries (using SQL)
  • Wrap $this->tag_name in a string_html_specialchars() call in IssueTagTimelineEvent::html()

Credits

MantisBT thanks Vishal Shukla for discovering and responsibly reporting the issue.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistmantisbt/mantisbt2.28.0&&< 2.28.22.28.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mantisbt/mantisbt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update mantisbt/mantisbt to 2.28.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-73vx-49mv-v8w5 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-73vx-49mv-v8w5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-73vx-49mv-v8w5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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. ### Impact Cross-site scripting (XSS). ### Patches f32787c14d4518476fe7f05f992dbfe6eaccd815 ### Workarounds * Edit offending History entries (using SQL) * Wrap `$this->tag_name` in a string_html_specialchars() call in IssueTagTimelineEvent::html() ### Credits MantisBT thanks Vishal Shukla for discovering and responsibly reporting the issue.
O3 Security · Impact-Aware SCA

Is GHSA-73vx-49mv-v8w5 in your dependencies?

O3 detects GHSA-73vx-49mv-v8w5 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.