CVE-2026-4268
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘wpgmza_custom_js’ parameter in all versions up to, and including, 10.0.05 due to insufficient input sanitization and output escaping and missing capability check in the 'admin_post_wpgmza_save_settings' hook anonymous function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP Go Maps (formerly WP Google Maps) WordPress plugin fails to properly sanitize and escape the 'wpgmza_custom_js' parameter before outputting it, combined with a missing capability check in the admin_post_wpgmza_save_settings hook. This allows authenticated users with Subscriber-level access to inject persistent malicious JavaScript that executes when other users access affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WP Go Maps plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate 'WP Go Maps' (formerly WP Google Maps). Note the version number displayed.Affected if Plugin is installed and version is 10.0.05 or earlier
-
Confirm plugin version is within affected rangeCompare the installed version number to the affected range. The vulnerability affects versions up to and including 10.0.05.Affected if Version is 10.0.05 or lower (any version below the patched release)
-
Check if plugin is activeIn Plugins > Instored Plugins, verify the WP Go Maps plugin status is 'Active'.Affected if Plugin is active and vulnerable version is installed
-
Inspect settings capability for wpgmza_custom_jsExamine the plugin settings page (Maps > Settings) or inspect the database option 'wpgmza_custom_js' in the wp_options table to see if custom JavaScript can be saved.Affected if Custom JavaScript field exists and can be modified by low-privilege users (Subscriber role)
-
Verify user role permissionsAttempt to access the plugin settings as a user with Subscriber role, or inspect the admin_post_wpgmza_save_settings hook capability check in the plugin code.Affected if Subscriber-level users can access and modify plugin settings including custom JS
A user is affected if WP Go Maps plugin version 10.0.05 or earlier is installed and active, and users with Subscriber-level access can modify the wpgmza_custom_js setting.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the WP Go Maps plugin to a version beyond 10.0.05 that includes the security patch, or remove/disable the plugin until a patched version is available.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4268 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4268 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data