CVE-2026-47156

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (52nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-75087 (ENISA EUVD) · GHSA-c2xg-qjqw-2v98 (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

MantisBT is an open source bug tracker. Versions 2.28.3 and earlier contain a critical authentication bypass in the SOAP API's mci_check_login() function. Any user knowing any valid cookie_string can authenticate as any other user (knowing their username), including the administrator, without knowing the target's password. The vulnerability is exploitable with zero prior access on default MantisBT installations because self-registration is enabled by default ($g_allow_signup = ON). A self-registered user can use their own cookie_string (readable from their browser's MANTIS_STRING_COOKIE cookie after login) to impersonate the administrator via the SOAP API. The REST API is NOT affected. The REST API's AuthMiddleware derives the username server-side from the API token or session cookie, so the username cannot be spoofed. The Web UI is NOT affected. The Web UI authenticates via PHP session cookies (PHPSESSID) and validates the MANTIS_STRING_COOKIE against the logged-in user through auth_is_cookie_valid(). The username is derived server-side from the cookie, not supplied by the client. Version 2.28.4 contains a patch. No known workarounds are available.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 15, 2026

Last Modified

September 10, 2026

Advisory Details (3)

Auto-updated Oct 3, 2026
Patch available. Sources: github_commit, github.
Web pageMentions a patch (unverified)

0037121: CVE-2026-47156: SOAP API Authentication Bypass -> Privilege Escalation to Administrator - MantisBT

https://mantisbt.org/bugs/view.php?id=37121
GitHub advisoryMentions a patch (unverified)

SOAP API Authentication Bypass with Privilege Escalation to Administrator · Advisory · mantisbt/mantisbt · GitHub

https://github.com/mantisbt/mantisbt/security/advisories/GHSA-c2xg-qjqw-2v98
GitHub commit

commit e3571c319b17 (mantisbt/mantisbt)

Fix landed in mantisbt/mantisbt commit e3571c319b17 — awaiting tagged release

https://github.com/mantisbt/mantisbt/commit/e3571c319b1721b41b0dc4b5b5203cbdcbe0c2ee

Vendor Advisories for CVE-2026-47156(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composermantisbt/mantisbt @ 2.28.4 (fixes <= 2.28.3)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
mantisbt/mantisbt2.10.0 ... 2.9.1 (78 versions)
  • every version up to 2.28.4: fixed in 2.28.4
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 59× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 07:59 UTCEG score recompute
  2. 2026-11-02 07:59 UTCGHSA enrichmentGHSA-c2xg-qjqw-2v98 · GitHub severity CRITICAL
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-11-01 08:13 UTCGHSA enrichmentGHSA-c2xg-qjqw-2v98 · GitHub severity CRITICAL
  5. 2026-11-01 07:47 UTCGHSA enrichmentGHSA-c2xg-qjqw-2v98 · GitHub severity CRITICAL
  6. 2026-11-01 07:47 UTCEG score recompute
  7. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-10-31 08:27 UTCEG score recompute
  9. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-30 08:42 UTCEG score recompute
  11. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-10-29 08:57 UTCEG score recompute
  13. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-28 09:07 UTCEG score recompute
  15. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-27 08:48 UTCEG score recompute
  17. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-26 07:22 UTCEG score recompute
  19. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-10-25 14:24 UTCEG score recompute
  21. 2026-10-25 07:38 UTCEG score recompute
  22. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-24 07:52 UTCEG score recompute
  24. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-23 08:07 UTCEG score recompute
Show 66 more
  1. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-10-22 08:19 UTCEG score recompute
  3. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-10-21 08:33 UTCEG score recompute
  5. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-20 08:46 UTCEG score recompute
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-19 08:58 UTCEG score recompute
  9. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-18 03:36 UTCEG score recompute
  11. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-17 07:17 UTCEG score recompute
  13. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-16 07:29 UTCEG score recompute
  15. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-15 06:24 UTCEG score recompute
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  18. 2026-10-14 02:04 UTCEG score recompute
  19. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-12 22:22 UTCEG score recompute
  21. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-10-12 16:02 UTCEG score recompute
  23. 2026-10-11 19:45 UTCEG score recompute
  24. 2026-10-11 16:59 UTCEG score recompute
  25. 2026-10-11 14:24 UTCEG score recompute
  26. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  28. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  30. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  32. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  34. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  36. 2026-10-01 12:40 UTCEG score recompute
  37. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  38. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  39. 2026-09-28 08:44 UTCEG score recompute
  40. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  41. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  42. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  43. 2026-09-24 08:50 UTCEG score recompute
  44. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  45. 2026-09-23 03:16 UTCEG score recompute
  46. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  47. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  48. 2026-09-18 04:45 UTCEG score recompute
  49. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  50. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  51. 2026-09-13 23:12 UTCEG score recompute
  52. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  53. 2026-09-12 16:48 UTCEG score recompute
  54. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  55. 2026-09-11 21:45 UTCEG score recompute
  56. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  57. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  58. 2026-09-10 15:28 UTCEG score recompute
  59. 2026-09-10 15:01 UTCEG score recompute
  60. 2026-09-09 17:34 UTCEG score recompute
  61. 2026-09-09 16:30 UTCEG score recomputeFirst assessed: 9.3 CRITICAL
  62. 2026-09-09 16:25 UTCMITRE cvelistV5CVSS v3 → 9.3 · CVSS v4 → 9.3
  63. 2026-08-01 09:23 UTCEG score recompute
  64. 2026-07-26 11:35 UTCEG score recompute
  65. 2026-07-23 03:17 UTCEG score recompute
  66. 2026-07-15 16:54 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-47156?
CVE-2026-47156 is a critical-severity vulnerability; its CVE record was published on July 15, 2026. MantisBT is an open source bug tracker. Versions 2.28.3 and earlier contain a critical authentication bypass in the SOAP API's mci_check_login() function. Any user knowing any valid cookie_string can authenticate as any other user (knowing their username), including the administrator, without…
When was the CVE record for CVE-2026-47156 published?
The CVE record for CVE-2026-47156 was published on July 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-47156 actively exploited?
CVE-2026-47156 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47156?
CVE-2026-47156 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47156?
A fix for CVE-2026-47156 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47156 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47156

Explore →

Is Your Infrastructure Affected by CVE-2026-47156?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs