Skip to main content
← All vulnerabilities
CVE-2026-118638

Mapster WP Maps < 2.0.6 - Unauthenticated Arbitrary Post Modification via save-mapmaker REST Route

Mapster WP Maps versions before 2.0.6 are affected. The vendor's rating is not given in the facts, and the fix is in 2.0.6.

Published
Last modified
published
Not listed in CISA KEV
Unclear
Fix
Fixed in 2.0.6
None on Exploit-DB, Metasploit or GitHub

Summary

The Mapster WP Maps WordPress plugin is affected, allowing unauthenticated attackers to modify arbitrary posts, create published posts, and overwrite the plugin's stored settings. This lets anyone on the internet alter site content and configuration without logging in.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

The Mapster WP Maps WordPress plugin before 2.0.6 does not perform any authorization check on a REST API route that writes post data, allowing unauthenticated attackers to overwrite the title of arbitrary posts, create arbitrary published posts, and overwrite the Mapster WP Maps WordPress plugin before 2.0.6's stored settings.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Unknown Mapster WP Maps

    fixed in 2.0.6

References 1

wpscan.com

FAQ

Questions about CVE-2026-118638

What does this mean?

The bug lets unauthenticated requests overwrite the title of arbitrary posts, create arbitrary published posts, and overwrite the plugin's stored settings through the save-mapmaker REST route.Source: wpscan.com

Am I affected, and how do I check?

The affected versions are Mapster WP Maps releases before 2.0.6. To check an installed copy, look at the plugin's version shown on the WordPress Plugins screen.Source: wpscan.com

What should I do about it?

Upgrade Mapster WP Maps to 2.0.6 or later, which is the listed fixed version.Source: wpscan.com

Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data