Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

GHSA-49w9-82cj-xr48

MEDIUMFix: mantisbt/mantisbt@3e37b40

GHSA-49w9-82cj-xr48 is a medium-severity (CVSS 5.3) SQL Injection vulnerability in mantisbt/mantisbt. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-49w9-82cj-xr48 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

MantisBT SQL Injection via mc_project_get_users function

Also known asCVE-2020-28413
Published
May 24, 2022
Updated
May 29, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of May 29, 2025 · OSV.dev, NVD, 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

In MantisBT 2.24.3, SQL Injection can occur in the parameter "access" of the mc_project_get_users function through the API SOAP.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistmantisbt/mantisbtall versions2.24.4
Exploits & PoCs
2

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

EDB-49340webappsphp

Mantis Bug Tracker 2.24.3 - 'access' SQL Injection

by EthicalHCOP · Jan 4, 2021

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

Frequently Asked Questions

In MantisBT 2.24.3, SQL Injection can occur in the parameter "access" of the mc_project_get_users function through the API SOAP.
O3 Security · Impact-Aware SCA

Is GHSA-49w9-82cj-xr48 in your dependencies?

O3 detects GHSA-49w9-82cj-xr48 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-49w9-82cj-xr48: MantisBT SQL… | O3 Security