CVE-2026-8839

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory published 2026-06-06. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 5.3Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The MapPress Maps for WordPress plugin for WordPress is vulnerable to Authorization Bypass Through User-Controlled Key in all versions up to, and including, 2.96.6. This is due to missing ownership verification in the REST API routes registered via Mappress_Api::rest_api_init(), where the GET /wp-json/mapp/v1/maps/{mapid} endpoint uses 'permission_callback' => '__return_true' and the write endpoints (POST update, DELETE, PATCH mutate, POST clone, POST empty_trash) only check the generic edit_posts capability without confirming that the requester owns the targeted map — a gap that is not compensated at the model layer, as Mappress_Map::get(), save(), delete(), mutate(), and empty_trash() all operate on any caller-supplied map ID without an ownership check. This makes it possible for unauthenticated attackers to read sensitive map data — including POI titles, addresses, coordinates, and body content — for any map on the site by enumerating map IDs, and for authenticated attackers with Contributor-level access and above to modify, delete, trash/restore, or clone any map regardless of its author.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation1.3% × 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 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.3%
EPSS %ILE
69th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (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.

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

June 6, 2026

Last Modified

July 23, 2026

References (24)

15 of 24 shown · show the other 9

Vendor Advisories for CVE-2026-8839(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 29× 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.

Showing the most recent 96 of 218 refreshes on record for this CVE.

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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:15 UTCEG score recompute
  2. 2026-10-11 16:32 UTCEG score recompute
  3. 2026-10-11 13:50 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  4. 2026-10-11 13:48 UTCEG score recompute
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  9. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  10. 2026-10-05 17:44 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  11. 2026-10-01 19:51 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  12. 2026-09-30 15:04 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  13. 2026-09-28 13:52 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  14. 2026-09-27 13:49 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  15. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  16. 2026-09-24 14:04 UTCEPSS rescoreEPSS 1.3% · 69th percentile
  17. 2026-09-23 17:54 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  18. 2026-09-22 16:01 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  19. 2026-09-21 21:09 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  21. 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  22. 2026-09-17 19:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  23. 2026-09-16 14:09 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  25. 2026-09-15 03:12 UTCEPSS rescoreEPSS 1.0% · 61st percentile
Show 71 more
  1. 2026-09-14 04:59 UTCEG score recompute
  2. 2026-09-14 04:59 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  3. 2026-09-13 16:48 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  4. 2026-09-12 15:02 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  5. 2026-09-11 14:53 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  6. 2026-09-11 09:38 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  7. 2026-09-08 22:01 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  8. 2026-09-06 13:48 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  9. 2026-09-05 15:31 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  10. 2026-09-04 05:07 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  11. 2026-09-02 14:12 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  12. 2026-09-01 13:54 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  13. 2026-09-01 04:40 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  14. 2026-08-30 19:18 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  15. 2026-08-30 01:22 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  16. 2026-08-28 21:42 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  17. 2026-08-27 14:25 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  18. 2026-08-26 14:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  19. 2026-08-25 13:49 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  20. 2026-08-25 01:48 UTCEG score recompute
  21. 2026-08-25 01:48 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  22. 2026-08-24 14:18 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  23. 2026-08-23 12:21 UTCEG score recompute
  24. 2026-08-23 12:21 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  25. 2026-08-23 00:19 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  26. 2026-08-21 23:49 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  27. 2026-08-21 08:28 UTCEG score recompute
  28. 2026-08-21 08:28 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  29. 2026-08-20 22:56 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  30. 2026-08-20 09:36 UTCEG score recompute
  31. 2026-08-20 09:36 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  32. 2026-08-19 17:04 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  33. 2026-08-18 13:49 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  34. 2026-08-17 13:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  35. 2026-08-17 09:59 UTCEG score recompute
  36. 2026-08-17 09:59 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  37. 2026-08-16 14:56 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  38. 2026-08-16 11:07 UTCEG score recompute
  39. 2026-08-16 11:07 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  40. 2026-08-16 02:15 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  41. 2026-08-15 12:16 UTCEG score recompute
  42. 2026-08-15 12:16 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  43. 2026-08-15 01:31 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  44. 2026-08-14 11:14 UTCEG score recompute
  45. 2026-08-14 11:14 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  46. 2026-08-13 22:00 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  47. 2026-08-13 12:22 UTCEG score recompute
  48. 2026-08-13 12:22 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  49. 2026-08-12 13:51 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  50. 2026-08-12 13:02 UTCEG score recompute
  51. 2026-08-12 13:02 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  52. 2026-08-11 13:43 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  53. 2026-08-11 13:42 UTCEG score recompute
  54. 2026-08-11 13:42 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  55. 2026-08-11 00:00 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  56. 2026-08-10 14:50 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  57. 2026-08-09 15:48 UTCEG score recompute
  58. 2026-08-09 15:48 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  59. 2026-08-09 13:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  60. 2026-08-08 16:57 UTCEG score recompute
  61. 2026-08-08 16:57 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  62. 2026-08-08 16:37 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  63. 2026-08-07 18:02 UTCEG score recompute
  64. 2026-08-07 18:02 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  65. 2026-08-07 16:30 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  66. 2026-08-06 19:10 UTCEG score recompute
  67. 2026-08-06 19:10 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  68. 2026-08-06 13:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  69. 2026-08-05 20:18 UTCEG score recompute
  70. 2026-08-05 20:18 UTCGHSA enrichmentGHSA-4m8c-59q5-hc8f · GitHub CVSS 5.3
  71. 2026-08-05 19:17 UTCEPSS rescoreEPSS 1.0% · 60th percentile

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-8839.yaml
    Published Jun 10, 2026

    WordPress MapPress Maps <= 2.96.6 - Unauthenticated IDOR

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8839?
CVE-2026-8839 is a medium-severity vulnerability; its CVE record was published on June 6, 2026. The MapPress Maps for WordPress plugin for WordPress is vulnerable to Authorization Bypass Through User-Controlled Key in all versions up to, and including, 2.96.6. This is due to missing ownership verification in the REST API routes registered via MappressApi::restapiinit(), where the GET…
When was the CVE record for CVE-2026-8839 published?
The CVE record for CVE-2026-8839 was published on June 6, 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-8839 actively exploited?
CVE-2026-8839 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (69th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8839?
CVE-2026-8839 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-8839?
No fix for CVE-2026-8839 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-8839 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-8839

Explore →

Is Your Infrastructure Affected by CVE-2026-8839?

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

Book a Demo →Browse All CVEs