CVE-2026-34390

MEDIUMNVD 5.15.1
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.1 under NVD CVSS. EPSS exploit probability: 0.4% (37th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS
Sources: EPSS, NVD CVSS
Elevated

Also known asEUVD-2026-30994 (ENISA EUVD) · GHSA-frf7-jhp9-jxm6 (GitHub Security Advisories)Source: ENISA EUVD

5.1EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Mantis Bug Tracker (MantisBT) is an open source issue tracker. Versions 2.28.1 and prior have a Privilege Escalation vulnerability where insufficient access control checks in ProjectUsersAddCommand (manage_proj_user_add.php) allow users having manage_project_threshold access level (manager by default) to grant project-level administrator access to any user (including themselves) in any Project they have manager rights in. The normal project-user add form restricts the selectable access levels to the actor's own project role or below. However, the backend handler still accepts a forged higher access_level value and writes it. The consequences of the privilege escalation are slight, as having administrator access at Project level is effectively not very different from being manager, and it does not actually give administrator privileges on the whole MantisBT instance. In particular, it does not let the upgraded user delete the Project or grant them any access to global administrative functions such as managing Users, Projects, Plugins, Custom Fields, etc. This issue has been fixed in version 2.28.2.

CVSS
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
54
EG Risk 54/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)
Severity51% × 45%
Impact severity (EG Severity): CVSS 5.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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.4%
EPSS %ILE
37th
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 (5.1): severity, escalated by confirmed exploitation. This CVE's 5.1 is its impact severity (EG Severity), not escalated.

EG Severity
5.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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: 14 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 public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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)14 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 partial (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

May 19, 2026

Last Modified

July 24, 2026

Advisory Details (4)

Auto-updated Jun 16, 2026
Patch available. Sources: github, github_commit.
Web page

0037002: Privilege Escalation Due to Improper Authorization in Project Role Assignment - MantisBT

https://mantisbt.org/bugs/view.php?id=37002
Web pageMentions a patch (unverified)

0036995: CVE-2026-34390: Privilege Escalation from Manager to Administrator role per project basis - MantisBT

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

Privilege Escalation from Manager to Project-level Administrator · Advisory · mantisbt/mantisbt · GitHub

https://github.com/mantisbt/mantisbt/security/advisories/GHSA-frf7-jhp9-jxm6
GitHub commit

commit 69e0180f180e (mantisbt/mantisbt)

Fix landed in mantisbt/mantisbt commit 69e0180f180e — awaiting tagged release

https://github.com/mantisbt/mantisbt/commit/69e0180f180ed5acf48a8d281a73683a7bf32461

Vendor Advisories for CVE-2026-34390(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.2 (fixes <= 2.28.1)—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 (76 versions)
  • every version up to 2.28.2: fixed in 2.28.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 32× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 230 rows on record for this CVE, as 98 entries (2 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  3. 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  5. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  6. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  8. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-11-01 07:53 UTCGHSA enrichmentGHSA-frf7-jhp9-jxm6 · GitHub severity MODERATE
  14. 2026-11-01 07:53 UTCEchelonGraph re-scored
  15. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-30 20:55 UTCOSV refresh
  17. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-10-25 14:34 UTCEchelonGraph re-scored
  24. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 73 more
  1. 2026-10-23 03:26 UTCEchelonGraph re-scored
  2. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-18 03:45 UTCEchelonGraph re-scored
  8. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-12 16:12 UTCEchelonGraph re-scored
  15. 2026-10-11 19:54 UTCEchelonGraph re-scored
  16. 2026-10-11 17:08 UTCEchelonGraph re-scored
  17. 2026-10-11 14:35 UTCEchelonGraph re-scored
  18. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  26. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  27. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  28. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  29. 2026-09-30 03:10 UTCOSV refresh
  30. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  31. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  32. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  33. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  34. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  35. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  36. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  37. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  38. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  39. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  40. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  41. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  42. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  43. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  44. 2026-09-11 05:23 UTCOSV refresh
  45. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  46. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  47. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  48. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  49. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  50. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  51. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  52. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  53. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  54. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  55. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  56. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  57. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  59. 2026-08-23 16:59 UTCEchelonGraph re-scored
  60. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  61. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  62. 2026-08-21 23:36 UTCEchelonGraph re-scored
  63. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  64. 2026-08-20 18:58 UTCEchelonGraph re-scored
  65. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  66. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  67. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  68. 2026-08-17 09:58 UTCEchelonGraph re-scored
  69. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  70. 2026-08-16 03:32 UTCEchelonGraph re-scored
  71. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  72. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  73. 2026-08-14 02:05 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-34390?
CVE-2026-34390 is a medium-severity vulnerability; its CVE record was published on May 19, 2026. Mantis Bug Tracker (MantisBT) is an open source issue tracker. Versions 2.28.1 and prior have a Privilege Escalation vulnerability where insufficient access control checks in ProjectUsersAddCommand (manage_proj_user_add.php) allow users having manage_project_threshold access level (manager by…
When was the CVE record for CVE-2026-34390 published?
The CVE record for CVE-2026-34390 was published on May 19, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-34390 actively exploited?
CVE-2026-34390 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-34390?
CVE-2026-34390 has a CVSS base score of 5.1 (NVD).
How do I remediate CVE-2026-34390?
A fix for CVE-2026-34390 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-34390 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-34390

Explore →

Is Your Infrastructure Affected by CVE-2026-34390?

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