GHSA-f633-865q-2mhh
Fix: mantisbt/mantisbt@44f490bGHSA-f633-865q-2mhh is a security vulnerability in mantisbt/mantisbt. O3 Security confirms whether GHSA-f633-865q-2mhh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
MantisBT is Vulnerable to Stored XSS in Saved-Filter Owner Column
Real-World Exposure
mantisbt/mantisbtReal-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
Incorrect escaping of a saved filter's owner allows an attacker to inject arbitrary HTML on systems where $g_show_user_realname = ON.
Impact
Cross-site scripting (XSS).
Note that By default, only users with Manager access level or above can save their filters publicly
Patches
- 44f490bcf20fd491c1b8f3fc9dd041d8c2a30010
Workarounds
- Prevent display of users' real name (set
$g_ show_user_realname = OFF;in configuration) - Restrict ability to store filters (set $
g_stored_query_create_threshold/ $g_stored_query_create_shared_thresholdtoNOBODY
Credits
Thanks to siunam (Tang Cheuk Hei) for discovering and responsibly reporting the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | mantisbt/mantisbt | ≥ 2.1.0&&< 2.28.2 | 2.28.2 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
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-f633-865q-2mhh is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-f633-865q-2mhh 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-f633-865q-2mhh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-f633-865q-2mhh in your dependencies?
O3 detects GHSA-f633-865q-2mhh across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.