PatchSiren cyber security CVE debrief
CVE-2026-12954 mapster CVE debrief
The Mapster WP Maps plugin for WordPress is vulnerable to Arbitrary User Meta Write in all versions up to, and including, 1.23.0. This vulnerability allows authenticated attackers, with Subscriber-level access and above, to update arbitrary user meta values. The vulnerability exists due to the `my_profile_update()` function performing no nonce verification, no capability check, and no allowlist validation on the meta key supplied via the `acf-photo-gallery-groups` POST parameter before passing both the meta key and its corresponding value directly to `update_user_meta()`.
- Vendor
- mapster
- Product
- Mapster WP Maps
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-18
- Original CVE updated
- 2026-09-19
- Advisory published
- 2026-09-18
- Advisory updated
- 2026-09-19
Who should care
Defenders responsible for WordPress installations with the Mapster WP Maps plugin should assess exposure and prioritize patching or mitigation. This includes reviewing the vulnerability in their inventory, applying necessary patches or mitigations, and monitoring for potential exploitation attempts.
Why it matters
The vulnerability allows authenticated attackers to update arbitrary user meta values, which can potentially be used to gain further access or disrupt site functionality.
- Authenticated attackers with Subscriber-level access and above can update arbitrary user meta values
- Privilege escalation is not possible, but arbitrary user meta values can be updated
Technical summary
The Mapster WP Maps plugin for WordPress is vulnerable to Arbitrary User Meta Write in all versions up to, and including, 1.23.0 via the `my_profile_update()` function. This is due to the function performing no nonce verification, no capability check, and no allowlist validation on the meta key supplied via the `acf-photo-gallery-groups` POST parameter before passing both the meta key and its corresponding value directly to `update_user_meta()`.
Defensive priority
Defenders should prioritize verifying the vulnerability in their inventory and applying the necessary patches or mitigations.
Recommended defensive actions
- Verify the vulnerability in your inventory
- Apply the necessary patches or mitigations
- Monitor for potential exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The vulnerability is due to the `my_profile_update()` function performing no nonce verification, no capability check, and no allowlist validation on the meta key supplied via the `acf-photo-gallery-groups` POST parameter before passing both the meta key and its corresponding value directly to `update_user_meta()`.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-12954 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-12954
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-12954 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-12954
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/mapster-wp-maps/tags/1.21.0/includes/acf-photo-gallery-field/includes/acf_photo_gallery_save.php
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/mapster-wp-maps/tags/1.23.0/includes/acf-photo-gallery-field/includes/acf_photo_gallery_save.php
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.