Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running vulnerable Mapster WP Maps
-
DeliverySend unauthenticated request to REST route
-
ExploitBypass missing authorization check
-
ExecutionOverwrite post titles and create published posts
-
ImpactOverwrite plugin stored settings
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The site must run Mapster WP Maps for WordPress at a version below 2.0.6 with the plugin active, exposing its REST API route that writes post data. No special configuration, feature toggle, user interaction, or authentication is required: per the CVSS vector (AV:N/AC:L/PR:N/UI:N) the vulnerable REST route performs no authorization check, so any remote unauthenticated attacker who can reach the site's WordPress REST API can trigger it against a default installation. The main limiting factor is deployment footprint - only sites with this specific plugin installed and not yet updated to 2.0.6 are affected; impact is confined to integrity (post titles, created posts, plugin settings) with no direct confidentiality or availability effect. |
| Impact | Signals here point to a moderate, not emergency, priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated flaw with high integrity impact and no confidentiality or availability impact - consistent with CWE-862 missing authorization on a REST route. SSVC reinforces partial technical impact and marks the issue Automatable:yes (a predictable unauthenticated REST endpoint can be scripted and sprayed), yet records Exploitation:none, meaning no observed exploitation. EPSS is low at 0.15% (4th percentile), and there is no CISA KEV listing, so there is currently no confirmed active exploitation - exploitation status is 'no public exploit identified at time of analysis'. These signals are internally consistent rather than conflicting: a genuinely easy-to-automate unauthenticated write primitive (which justifies the vuln.today 'this_week' label) against a product whose real-world footprint is small, so broad opportunistic exploitation has not materialized. The 'Authentication Bypass' tag is imprecise - CWE-862 is a missing authorization check, so the attacker needs no credentials to bypass because none are checked, rather than defeating an authentication mechanism. Net: a legitimate access-control defect to patch promptly on affected sites, but not a CVSS-inflated non-issue nor a widespread emergency. |
| Exploit ScenarioDerived | An unauthenticated attacker discovers a WordPress site running Mapster WP Maps before 2.0.6 and sends crafted requests directly to the plugin's unauthorized REST API route. Because no authorization check is performed, the attacker overwrites arbitrary post titles, injects new published posts (enabling defacement, spam, or SEO/phishing content), and overwrites the plugin's stored settings. No public exploit code has been identified at the time of analysis, but the low-complexity, no-interaction network vector makes the attack straightforward to automate. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 01, 2026
Unauthenticated remote attackers can overwrite the titles of arbitrary posts, create arbitrary published posts, and rewrite the stored settings of the Mapster WP Maps WordPress plugin at versions below 2.0.6, because one of its REST API routes that writes post data performs no authorization check. Any site with the plugin active and reachable over HTTP is exposed, with the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, integrity-only) confirming no authentication, interaction or special configuration is needed. Impact is confined to integrity of content and plugin configuration, with no direct confidentiality or availability effect; there is no confirmed active exploitation (CISA KEV not listed, SSVC exploitation: none), no public exploit identified at time of analysis, and EPSS is low at 0.15 percent (4th percentile), though the flaw is automatable and is prioritized for patching this week. A vendor fix is available in 2.0.6.
RemediationAI
Vendor-released patch: update Mapster WP Maps to version 2.0.6 or later, which is the only complete fix identified in the available data; the advisory at https://wpscan.com/vulnerability/3d3004f1-46f1-479d-bae6-754e56d3aa7e/ should be used to confirm the fixed build and check for any follow-on notes. If the update cannot be applied immediately, removing exposure means deactivating and removing the plugin until it can be updated, since the vulnerable route is registered by the plugin itself and is unreachable once the plugin is inactive; the trade-off is loss of the maps functionality on the site. Because the route performs no authorization check, no role, nonce or configuration change short of disabling the plugin or blocking access to the WordPress REST API path closes the hole, and blocking /wp-json/ site-wide has the side effect of breaking other plugins and blocks that depend on REST. Given the automatable nature of the flaw and this-week prioritization, schedule the 2.0.6 upgrade rather than relying on compensating controls.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-862 (Missing Authorization) in a WordPress plugin's REST API surface. WordPress exposes plugin-defined routes through register_rest_route(), where each route supplies a permission_callback that is supposed to gate access before the handler runs; when that callback is absent or effectively permissive, the route inherits the open-by-default REST behavior and can be invoked by anyone who can reach /wp-json/. Here the affected route writes post data, so the missing check lets an unauthenticated caller pass content through the handler's write path, which is why the observed outcomes are title overwrites on arbitrary posts, creation of new published posts, and replacement of the plugin's stored settings. The integrity-only scoring (C:N/I:H/A:N) reflects that the defect is an authorization gap on a write operation rather than a code-execution or data-disclosure primitive. Per the assessed conditions, exploitation requires only an active installation below 2.0.6 whose REST API is reachable - no feature toggle, role, nonce or user interaction is involved - and the practical limiting factor is deployment footprint rather than any technical precondition. The mechanism by which the handler accepts and persists the supplied post data is not further described in the available sources.
Know when WordPress gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Unauthenticated network REST route with no authorization check gives PR:N/AC:L/UI:N; impact is arbitrary content/settings writes, so I:H with C:N and A:N.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
4DescriptionCVE.org
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.
Executive ViewAI
CVE-2026-118638 is a high-severity vulnerability in the Mapster WP Maps WordPress plugin (versions below 2.0.6) that allows unauthenticated attackers to modify website content and settings. This could lead to reputational damage, misinformation, and operational disruption for any organization using the plugin, as attackers can overwrite posts and alter plugin configurations without authentication. Leadership should prioritize patching to maintain website integrity and trust.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-114588
GHSA-gwmh-v933-p43v
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB