The Mapster WP Maps WordPress plugin before 2.0.6 does not perform any authorization check on a REST API route that
Source GCVE Database
Not known to be exploited : upgrade to 2.0.6 soon.
Data as of 31 Oct 2026, 07:08 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.0.6
Exploitation evidence
Disclosed: evidence found.
CVE published 31 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Mapster WP Maps to 2.0.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mapster WP Maps | Affected
| Fixed in
|
AI-suggested
Upgrade the Mapster WP Maps WordPress plugin to version 2.0.6 or later, where this authorization check vulnerability has been fixed. No other mitigation is indicated.
Description
The Mapster WP Maps WordPress plugin versions prior to 2.0.6 contain a vulnerability where a REST API route that modifies post data lacks authorization checks. This flaw allows unauthenticated attackers to overwrite post titles, create new published posts, and alter the plugin's stored settings.