CVE-2026-8839

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

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, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: Elevated riskExposed: 0

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

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.3(medium)
EG Risk
55(Track)
EG Risk 55/100SSVC: Track

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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
61%
KEV
Not listed

Published

June 6, 2026

Last Modified

July 23, 2026

References (24)

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 / 75× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 180 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-8839.yaml
    First seen Jan 1, 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 vulnerability 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 CVE-2026-8839 disclosed?
CVE-2026-8839 was first published in the National Vulnerability Database on June 6, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8839 actively exploited?
CVE-2026-8839 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 39.2% of all scored CVEs.
What is the CVSS score of CVE-2026-8839?
CVE-2026-8839 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-8839?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8839, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs