dbcve.org
Google Map ShortcodeWordPress extension · Google Map Shortcode Project

CVE-2023-35772

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-19
Fix available
A fix is available. Upgrade to after 3.1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Alain Gonzalez Google Map Shortcode plugin <= 3.1.2 versions.

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 · moderate confidence

Unauthenticated reflected cross-site scripting (XSS) vulnerability in the Alain Gonzalez Google Map Shortcode WordPress plugin (versions 3.1.2 and below). Attackers can inject malicious JavaScript code through unsanitized user input that gets reflected back to victim browsers without proper output encoding.

MitigationUpdate the plugin to the latest version which contains proper input sanitization and output encoding. If no update is available, disable the plugin until a patched version is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Google Map ShortcodeWordPress extension
Affected:<= 3.1.2

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation
    Navigate to WordPress admin > Plugins and locate 'Google Map Shortcode' by Alain Gonzalez in the installed plugins list
    Affected if The plugin is not installed means they are not affected; if present, continue to version check
  2. Check installed version
    In the Plugins list, look at the version number displayed under the plugin name, or check the plugin header in /wp-content/plugins/google-map-shortcode/ folder for the Version: field
    Affected if Version 3.1.2 or any version lower indicates the plugin contains the vulnerability
  3. Identify shortcode usage
    Search your WordPress posts, pages, and custom post types for the [google_map_shortcode] or [ggmap] shortcode by searching the wp_posts table or using a search plugin
    Affected if If the shortcode is present anywhere, the vulnerable code path exists in your environment even if not actively exploited
  4. Check shortcode parameters in use
    Examine each instance of the shortcode for parameters that accept user input, particularly 'address', 'location', or similar location-related attributes that could be manipulated
    Affected if If the shortcode accepts user-supplied address/location parameters without server-side validation, the XSS payload could be injected

You are affected if the Google Map Shortcode plugin versions 3.1.2 or below is installed and the shortcode is being used with user-controlled input parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 3.1.2
Interim mitigation

Update the plugin to the latest version which contains proper input sanitization and output encoding. If no update is available, disable the plugin until a patched version is released.

Recommended fix Moderate confidence

Latest version beyond 3.1.2 (check WordPress plugin repository for current security release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Google Map Shortcode' plugin by Alain Gonzalez
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the updated plugin from the official WordPress plugin repository and upload it manually
  6. 6. After updating, verify the plugin is functioning correctly on the site

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Google Map Shortcode Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35772 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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