How severe is GHSA-9x76-mp7r-2xc5?

GHSA-9x76-mp7r-2xc5 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-9x76-mp7r-2xc5?

GHSA-9x76-mp7r-2xc5 affects the following packages: mantisbt/mantisbt (Packagist), mantisbt/mantisbt (Packagist), mantisbt/mantisbt (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-9x76-mp7r-2xc5?

Update mantisbt/mantisbt to 1.3.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9x76-mp7r-2xc5 is resolved across your whole dependency graph.

How do I detect GHSA-9x76-mp7r-2xc5 in my Packagist dependencies?

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.

How do I mitigate GHSA-9x76-mp7r-2xc5 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-9x76-mp7r-2xc5?

O3 pinpoints whether GHSA-9x76-mp7r-2xc5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9x76-mp7r-2xc5 actively exploited in the wild?

Yes. There are 3 known exploit references for GHSA-9x76-mp7r-2xc5, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-9x76-mp7r-2xc5?

GHSA-9x76-mp7r-2xc5 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 68th 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-9x76-mp7r-2xc5?

GHSA-9x76-mp7r-2xc5 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9x76-mp7r-2xc5 published, and has it been updated?

GHSA-9x76-mp7r-2xc5 was published on May 17, 2022 and was last updated on April 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-9x76-mp7r-2xc5

MEDIUM

MantisBT vulnerable to CSRF and Open Redirect attacks

Also known asCVE-2017-7620

Published

May 17, 2022

Updated

Apr 22, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk68th percentile+1.03%

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

3 pkgs affected

🐘mantisbt/mantisbt🐘mantisbt/mantisbt🐘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

MantisBT before 1.3.11, 2.x before 2.3.3, and 2.4.x before 2.4.1 omits a backslash check in string_api.php and consequently has conflicting interpretations of an initial / substring as introducing either a local pathname or a remote hostname, which leads to (1) arbitrary Permalink Injection via CSRF attacks on a permalink_page.php?url= URI and (2) an open redirect via a login_page.php?return= URI.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mantisbt/mantisbt`	all versions	1.3.11
🐘Packagist	`mantisbt/mantisbt`	≥ 2.0.0&&< 2.3.3	2.3.3
🐘Packagist	`mantisbt/mantisbt`	≥ 2.4.0&&< 2.4.1	2.4.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-42043webappsphp

Mantis Bug Tracker 1.3.10/2.3.0 - Cross-Site Request Forgery

by hyp3rlinx · May 20, 2017

Exploit-DB Source

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. 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 1.3.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9x76-mp7r-2xc5 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-9x76-mp7r-2xc5 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-9x76-mp7r-2xc5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

MantisBT before 1.3.11, 2.x before 2.3.3, and 2.4.x before 2.4.1 omits a backslash check in string_api.php and consequently has conflicting interpretations of an initial \/ substring as introducing either a local pathname or a remote hostname, which leads to (1) arbitrary Permalink Injection via CSRF attacks on a permalink_page.php?url= URI and (2) an open redirect via a login_page.php?return= URI.

O3 Security · Impact-Aware SCA

Is GHSA-9x76-mp7r-2xc5 in your dependencies?

O3 detects GHSA-9x76-mp7r-2xc5 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works