CVE-2026-7464
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 Google Maps Integration plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the `page` parameter in all versions up to, and including, 1.2. This is due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick an administrator into performing an action such as clicking on a link.
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 Google Maps Integration plugin for WordPress versions up to 1.2 contains a reflected Cross-Site Scripting (XSS) vulnerability due to insufficient input sanitization of the `page` parameter and inadequate output escaping. Unauthenticated attackers can inject arbitrary JavaScript through a maliciously crafted URL that, when clicked by an authenticated administrator, executes in the context of the admin session.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'WP Google Maps Integration'. Check the version number displayed below the plugin name, or inspect the plugin header in /wp-content/plugins/ directory.Affected if Installed version is 1.2 or lower (the vulnerable version range is 'up to 1.2')
-
Confirm admin access is availableThe vulnerability requires an authenticated administrator to click a malicious URL. Verify that administrator accounts exist and can access the WordPress admin dashboard.Affected if At least one administrator account is active and able to log in to the WordPress admin area
-
Test for reflected XSS in page parameterWhile authenticated as administrator, inspect URLs in the WP Google Maps plugin admin pages. Look for any usage of a 'page' parameter in the URL query string. Craft a test URL with a benign payload like ?page=test"><script>alert(1)</script> and observe if it reflects unescaped in the response.Affected if The 'page' parameter value reflects in the HTML output without proper sanitization or escaping
You are affected if the WP Google Maps Integration plugin is installed at version 1.2 or lower AND an administrator can be tricked into clicking a maliciously crafted URL containing the vulnerable 'page' parameter.
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.
dbcve · scopedUpdate the WP Google Maps Integration plugin to the latest version once available. Until then, implement a Web Application Firewall (WAF) rule to block requests with suspicious patterns in the `page` parameter and educate administrators about not clicking untrusted links.
Version higher than 1.2
- Update the WP Google Maps Integration plugin to the latest available version in the WordPress plugin repository
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7464 — 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-7464 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