dbcve.org
Wp Go MapsWordPress extension · Codecabin

CVE-2024-5994

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-14
Fix available
A fix is available. Upgrade to 9.0.39 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The WP Go Maps (formerly WP Google Maps) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Custom JS option in versions up to, and including, 9.0.38. This makes it possible for authenticated attackers that have been explicitly granted permissions by an administrator, with contributor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Version 9.0.39 adds a caution to make administrators aware of the possibility for abuse if permissions are granted to lower-level users.

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 confidence

The WP Go Maps WordPress plugin up to version 9.0.38 contains a stored XSS vulnerability in its Custom JS feature. Authenticated users with contributor-level or higher permissions can inject arbitrary JavaScript that executes when other users access pages containing the affected maps.

MitigationUpdate to version 9.0.39 or later and restrict the Custom JS permission to administrator-level users only, reviewing all existing user roles with access.

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
Wp Go MapsWordPress extension
Affected:< 9.0.39

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 WP Go Maps plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'WP Go Maps' (may also appear as 'WordPress Google Maps' or 'WPGM') in the list.
    Affected if Plugin is not found in the installed plugins list.
  2. Check installed plugin version
    In the plugins list, click on the plugin to view details, or check the version number displayed next to WP Go Maps. Compare against version 9.0.39.
    Affected if Installed version is 9.0.38 or lower.
  3. Confirm Custom JS feature is accessible to low-privilege users
    Navigate to Maps > Settings (or WPGM > Settings) in the WordPress admin panel. Look for a 'Custom JS' or 'Custom JavaScript' option. Check if users with 'Contributor' or 'Author' roles have permission to access this feature.
    Affected if Custom JS setting exists and is accessible to Contributor, Author, or Editor roles.
  4. Inspect existing Custom JS entries
    In the Custom JS settings panel, examine any custom JavaScript code that may already be saved. Look for suspicious script tags, event handlers (onerror, onload, onclick), or encoded characters that may indicate injected malicious code.
    Affected if Any unrecognized or encoded JavaScript is present in the Custom JS field.

You are affected if WP Go Maps version is below 9.0.39 AND the Custom JS feature is enabled for non-administrator user accounts.

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 9.0.39 or later
Fixed in 9.0.39
Interim mitigation

Update to version 9.0.39 or later and restrict the Custom JS permission to administrator-level users only, reviewing all existing user roles with access.

Recommended fix High confidence

9.0.39

  1. Update the WP Go Maps plugin to version 9.0.39 or later through the WordPress plugin administration panel
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate WP Go Maps (formerly WP Google Maps) in the list
  4. Click Update Now to install the latest version
  5. Alternatively, navigate to Dashboard > Updates and click Update Now for the plugin

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

Fix this in Wp Go Maps Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
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,624.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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