MapPress Maps for WordPress Plugin Vulnerability (CVE-2026-8839)

On this page

Security Alert Summary

The MapPress Maps for WordPress plugin contains an authorization bypass (CVE-2026-8839) in its REST API and model layer in all versions up to and including 2.96.6. Missing ownership checks in API route registration and model methods allow unauthenticated access to map data and permit authenticated users with Contributor-level access and above to alter maps they do not own.


CVE Details

  • CVE ID: CVE-2026-8839
  • Affected component: MapPress Maps for WordPress plugin
  • Affected versions: All versions up to and including 2.96.6
  • Published: June 6, 2026 at 5:16:29 AM UTC
  • Last modified: June 6, 2026 at 5:16:29 AM UTC
  • CVSS v3.1: Base score 5.3, MEDIUM — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
  • Authentication / privileges / user interaction: PrivilegesRequired: NONE, UserInteraction: NONE; initial read endpoint allows unauthenticated access, write actions require standard edit capability but lack ownership checks
  • Primary impact: Confidentiality: None; Integrity: Low; Availability: None
  • Weakness (CWE): CWE-639

Technical Details

The plugin registers REST API routes in Mappress_Api::rest_api_init(). The GET map endpoint /wp-json/mapp/v1/maps/{mapid} is registered with permission_callback set to '__return_true', allowing unauthenticated requests to read map records. Write endpoints (POST update, DELETE, PATCH mutate, POST clone, POST empty_trash) only verify the generic edit_posts capability and do not confirm that the requester owns the targeted map.

This lack of ownership verification is not compensated at the model layer: the methods Mappress_Map::get(), save(), delete(), mutate(), and empty_trash() operate on any caller-supplied map ID without additional author checks. As a result, unauthenticated attackers can enumerate map IDs and read point-of-interest details (titles, addresses, coordinates, body content). Authenticated users with Contributor-level access and above can modify, delete, trash/restore, or clone maps regardless of the map author.


How This Could Impact Your Website

Consider a site with a site owner, an internal editor, and an external contributor who manages location data. An unauthenticated attacker enumerating map IDs could retrieve POI titles, addresses, coordinates, and body content created by any user. That exposed contact and location information could be used to craft targeted phishing or social engineering campaigns against staff or external partners.

Separately, a contributor or contractor with standard editing privileges could alter or remove maps they do not own, potentially disrupting content that internal staff and visitors rely on. This can lead to incorrect public-facing location information and additional administrative overhead to detect and restore legitimate content.

If you
re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review your setup.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially Contributor and similar roles with edit capabilities.
  • Enforce strong passwords and two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins.
  • Monitor site activity and audit logs for unusual behavior related to maps and REST API access.

If you
like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References