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.
CVE-2026-8839
Score 5.3 from GitHub Security Advisory published 2026-06-06. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EPSS
- 52.6%
- KEV
- Not listed
Published
June 6, 2026
Last Modified
June 8, 2026
References (24)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_api.php#L253
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_api.php#L268
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_api.php#L328
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_api.php#L39
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_api.php#L50
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_api.php#L75
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_api.php#L90
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_map.php#L239
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_map.php#L379
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_map.php#L493
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.95.10/mappress_map.php#L550
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.96.6/mappress_api.php#L253
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.96.6/mappress_api.php#L268
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.96.6/mappress_api.php#L328
- security@wordfencehttps://plugins.trac.wordpress.org/browser/mappress-google-maps-for-wordpress/tags/2.96.6/mappress_api.php#L39
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 22× in last 7d / 93× 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.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 19:13 UTCEG score recompute
- 2026-07-05 19:13 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 20:21 UTCEG score recompute
- 2026-07-04 20:21 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 16:34 UTCEG score recompute
- 2026-07-03 16:34 UTCGHSA enrichment
- 2026-07-02 14:38 UTCEG score recompute
- 2026-07-02 14:38 UTCGHSA enrichment
- 2026-07-01 15:46 UTCEG score recompute
- 2026-07-01 15:46 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 16:51 UTCEG score recompute
- 2026-06-30 16:51 UTCGHSA enrichment
- 2026-06-29 16:18 UTCEG score recompute
- 2026-06-29 16:17 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
Show 72 moreShow fewer
- 2026-06-28 17:21 UTCEG score recompute
- 2026-06-28 17:21 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 18:29 UTCEG score recompute
- 2026-06-27 18:29 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 19:37 UTCEG score recompute
- 2026-06-26 19:37 UTCGHSA enrichment
- 2026-06-25 20:45 UTCEG score recompute
- 2026-06-25 20:45 UTCGHSA enrichment
- 2026-06-25 13:50 UTCEPSS rescore
- 2026-06-24 21:52 UTCEG score recompute
- 2026-06-24 21:52 UTCGHSA enrichment
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 23:00 UTCEG score recompute
- 2026-06-23 23:00 UTCGHSA enrichment
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 22:56 UTCEG score recompute
- 2026-06-22 22:55 UTCGHSA enrichment
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 20:33 UTCEG score recompute
- 2026-06-21 20:33 UTCGHSA enrichment
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-20 13:59 UTCEG score recompute
- 2026-06-20 13:59 UTCGHSA enrichment
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 15:07 UTCEG score recompute
- 2026-06-19 15:07 UTCGHSA enrichment
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 16:07 UTCEG score recompute
- 2026-06-18 16:07 UTCGHSA enrichment
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 17:14 UTCEG score recompute
- 2026-06-17 17:14 UTCGHSA enrichment
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-16 17:28 UTCEG score recompute
- 2026-06-16 17:28 UTCGHSA enrichment
- 2026-06-15 18:35 UTCEG score recompute
- 2026-06-15 18:35 UTCGHSA enrichment
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 18:40 UTCEG score recompute
- 2026-06-14 18:40 UTCGHSA enrichment
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 19:48 UTCEG score recompute
- 2026-06-13 19:48 UTCGHSA enrichment
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 20:52 UTCEG score recompute
- 2026-06-12 20:52 UTCGHSA enrichment
- 2026-06-11 22:01 UTCEG score recompute
- 2026-06-11 22:01 UTCGHSA enrichment
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-10 23:08 UTCEG score recompute
- 2026-06-10 23:08 UTCGHSA enrichment
- 2026-06-10 22:19 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 00:16 UTCEG score recompute
- 2026-06-10 00:16 UTCGHSA enrichment
- 2026-06-09 01:24 UTCEG score recompute
- 2026-06-09 01:24 UTCGHSA enrichment
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 02:32 UTCEG score recompute
- 2026-06-08 02:32 UTCGHSA enrichment
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 03:40 UTCEG score recompute
- 2026-06-07 03:40 UTCGHSA enrichment
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 04:48 UTCEG score recompute
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.yamlFirst seen Jan 1, 2026
WordPress MapPress Maps <= 2.96.6 - Unauthenticated IDOR
Open source ↗
Frequently asked(5)
What is CVE-2026-8839?
When was CVE-2026-8839 disclosed?
Is CVE-2026-8839 actively exploited?
What is the CVSS score of CVE-2026-8839?
How do I remediate CVE-2026-8839?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-8839
Is Your Infrastructure Affected by CVE-2026-8839?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.