dbcve.org
Google Map LocationsWordPress extension · Dotsquares

CVE-2024-49606

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-20
Fix available
A fix is available. Upgrade to after 1.0 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in DotsquaresLtd Google Map Locations google-map-locations allows Reflected XSS.This issue affects Google Map Locations: from n/a through <= 1.0.

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

A reflected cross-site scripting (XSS) vulnerability exists in the DotsquaresLtd Google Map Locations WordPress plugin. The vulnerability allows unauthenticated attackers to inject malicious JavaScript code through user-supplied input that is improperly sanitized and echoed back in the web page response. When victim users click crafted links or submit forms, the injected script executes in their browsers, potentially stealing session cookies or performing actions on behalf of the user.

MitigationSanitize all user-supplied input using WordPress sanitization functions (sanitize_text_field, esc_attr, etc.) and encode output using appropriate escaping functions (esc_html, esc_js, esc_url) before displaying in HTML contexts.

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 LocationsWordPress extension
Affected:<= 1.0

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 the Dotsquares Google Map Locations plugin is installed
    Log in to WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Dotsquares Google Map Locations' or similar naming in the list of active/inactive plugins.
    Affected if The plugin appears in the installed plugins list, regardless of activation status
  2. Check the installed plugin version
    In the Plugins list, click on the plugin name or view its details to read the Version number. Compare this to the affected version range of <= 1.0.
    Affected if The installed version is 1.0 or any version number lower than 1.0
  3. Identify if the plugin handles user-supplied input
    Inspect the plugin files (typically in wp-content/plugins/ directory under a folder named 'google-map-locations' or similar). Look for PHP files that process $_GET, $_POST, or $_REQUEST superglobals and output them directly to the page.
    Affected if The plugin contains code that takes user input (search fields, form submissions, URL parameters) and echoes it back in HTML response without using WordPress sanitization functions like sanitize_text_field, esc_attr, or esc_html
  4. Test for reflected XSS in URL parameters
    If the plugin provides any public-facing functionality (search, forms, map parameters), manually inject a test string like <script>alert('XSS')</script> into visible input fields or URL parameters and observe if the script executes in the browser.
    Affected if The injected script tag appears verbatim in the page source or executes when the page loads, indicating the input is reflected without proper encoding

You are affected if the Dotsquares Google Map Locations plugin is installed with version 1.0 or lower and the plugin reflects user-supplied input in its output without proper sanitization and escaping.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0
Interim mitigation

Sanitize all user-supplied input using WordPress sanitization functions (sanitize_text_field, esc_attr, etc.) and encode output using appropriate escaping functions (esc_html, esc_js, esc_url) before displaying in HTML contexts.

Fix this in Google Map Locations Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,220
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49606 — 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-2024-49606 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