dbcve.org
Wp Gpx MapsWordPress extension · Devfarm

CVE-2024-9028

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to after 1.7.08 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 GPX Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'sgpx' shortcode in all versions up to, and including, 1.7.08 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-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 confidence

The WP GPX Maps WordPress plugin fails to sanitize and escape user-supplied attributes in its 'sgpx' shortcode, allowing authenticated users with contributor-level access to inject malicious JavaScript that executes in browsers of users viewing affected pages. This is a stored XSS vulnerability stemming from insufficient input sanitization and output escaping.

MitigationUpdate the plugin to a version beyond 1.7.08 that implements proper sanitization (e.g., sanitize_text_field, esc_attr) on shortcode attributes and output escaping (e.g., esc_html, esc_attr) when rendering them, or remove/disable the sgpx shortcode until a patch is available.

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 Gpx MapsWordPress extension
Affected:<= 1.7.08

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 GPX Maps plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP GPX Maps' by Devfarm. Alternatively, check the /wp-content/plugins/wp-gpx-maps/ directory exists on the server.
    Affected if The plugin is installed and active
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the WP GPX Maps plugin name. Compare this version to the affected range: <= 1.7.08
    Affected if The installed version is 1.7.08 or lower
  3. Identify usage of the sgpx shortcode
    Search the WordPress database for posts/pages containing the '[sgpx' shortcode. This can be done via wp-admin > Posts > All Posts using the search function, or by querying the wp_posts table for posts containing 'sgpx' in post_content.
    Affected if Any post or page contains the sgpx shortcode with user-supplied attributes
  4. Check for contributor-level user accounts
    In WordPress admin, go to Users > All Users and review the roles assigned. Contributor role users can create shortcode content but typically cannot publish directly.
    Affected if Any authenticated user with contributor-level or higher access can edit content containing the shortcode

You are affected if WP GPX Maps plugin version 1.7.08 or lower is installed, active, and the sgpx shortcode is present in any content that can be edited by contributor-level or higher users.

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 1.7.08
Interim mitigation

Update the plugin to a version beyond 1.7.08 that implements proper sanitization (e.g., sanitize_text_field, esc_attr) on shortcode attributes and output escaping (e.g., esc_html, esc_attr) when rendering them, or remove/disable the sgpx shortcode until a patch is available.

Recommended fix Moderate confidence

Version 1.7.09 or later (check WordPress plugin repository for latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WP GPX Maps' plugin
  4. Check if an update is available (version higher than 1.7.08)
  5. If update available, click 'Update Now' to install the latest fixed version
  6. Alternatively, navigate to Dashboard > Updates to update all plugins
  7. After update, verify the plugin version is higher than 1.7.08

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

Fix this in Wp Gpx Maps Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,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 $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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