How severe is GHSA-fh48-f69w-7vmp?

No CVSS score has been assigned to GHSA-fh48-f69w-7vmp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fh48-f69w-7vmp?

GHSA-fh48-f69w-7vmp affects the following packages: mantisbt/mantisbt (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-fh48-f69w-7vmp?

Update mantisbt/mantisbt to 2.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fh48-f69w-7vmp is resolved across your whole dependency graph.

How do I detect GHSA-fh48-f69w-7vmp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mantisbt/mantisbt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fh48-f69w-7vmp if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-fh48-f69w-7vmp actively exploited in the wild?

No public exploit code has been indexed for GHSA-fh48-f69w-7vmp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-fh48-f69w-7vmp?

GHSA-fh48-f69w-7vmp has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fh48-f69w-7vmp?

GHSA-fh48-f69w-7vmp is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-fh48-f69w-7vmp published, and has it been updated?

GHSA-fh48-f69w-7vmp was published on March 25, 2026 and was last updated on March 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-fh48-f69w-7vmp — mantisbt/mantisbt

Fix: mantisbt/mantisbt@80990f4

GHSA-fh48-f69w-7vmp is a Cross-site Scripting (XSS) vulnerability in mantisbt/mantisbt. A fix is available for mantisbt/mantisbt — see the affected versions and patch details below.

MantisBT Vulnerable to Stored HTML Injection in Tag Delete Confirmation

Also known asCVE-2026-33517

Published

Mar 25, 2026

Updated

Mar 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fh48-f69w-7vmp.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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 name when deleting it in tag_delete.php allows an attacker to inject HTML and, if CSP settings permit, achieve execution of arbitrary JavaScript.

Impact

Cross-site scripting (XSS).

Patches

80990f43153167c73f11eb4b2bc7108d0c3d6b46

Workarounds

Revert commit d6890320752ecf37bd74d11fe14fe7dc12335be9
Manually edit language files to remove the sprintf placeholder %1$s from $s_tag_delete_message string, for example with sed -r -i '/tag_delete_message/s/.%1\$s.//' -- lang/

Credits

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mantisbt/mantisbt`	≥ 2.28.0&&< 2.28.1	2.28.1`composer require mantisbt/mantisbt:^2.28.1`

Affected Products

1 product · 1 configurations

Application

mantisbtmantisbt

1 version

2.28.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mantisbt/mantisbt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mantisbt/mantisbt to 2.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fh48-f69w-7vmp is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Improper escaping of Tag name when deleting it in tag_delete.php allows an attacker to inject HTML and, if CSP settings permit, achieve execution of arbitrary JavaScript. ### Impact Cross-site scripting (XSS). ### Patches 80990f43153167c73f11eb4b2bc7108d0c3d6b46 ### Workarounds * Revert commit d6890320752ecf37bd74d11fe14fe7dc12335be9 * Manually edit language files to remove the sprintf placeholder `%1$s` from *$s_tag_delete_message* string, for example with `sed -r -i '/tag_delete_message/s/.%1\$s.//' -- lang/` ### Credits MantisBT hanks Vishal Shukla for discovering and responsibly repor

O3 Security · Impact-Aware SCA

Is GHSA-fh48-f69w-7vmp in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works