dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-10629

HIGH · 8.8 CVSS v3.1 Published 2024-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 GPX Viewer plugin for WordPress is vulnerable to arbitrary file creation due to a missing capability check and file type validation in the gpxv_file_upload() function in all versions up to, and including, 2.2.9. This makes it possible for authenticated attackers, with subscriber-level access and above, to create arbitrary files on the affected site's server which may make remote code execution possible.

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 GPX Viewer WordPress plugin (versions up to 2.2.9) lacks proper authorization checks and file type validation in its gpxv_file_upload() function. Any authenticated user with subscriber-level permissions can invoke this function to create arbitrary files on the server, potentially achieving remote code execution by uploading malicious PHP files or other executable content.

MitigationUpdate to the latest version of GPX Viewer (2.3.0+) which includes proper capability checks and file type validation. If no update is available, disable the plugin immediately to prevent exploitation.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Confirm GPX Viewer plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'GPX Viewer' in the list, or inspect the plugin directory at wp-content/plugins/ for a folder named 'gpx-viewer' or similar
    Affected if The GPX Viewer plugin is present in the WordPress installation
  2. Identify the installed version
    In WordPress admin, click on the plugin name to view details and read the version number from the plugin header, or open the main plugin PHP file (usually gpx-viewer.php or similar in the plugin folder) and look for the 'Version:' comment in the file header
    Affected if The version displayed is 2.2.9 or lower (any version up to and including 2.2.9)
  3. Verify the file upload function exists
    Locate the plugin files and search for the function named 'gpxv_file_upload' within the PHP files, or check if an AJAX action handler or form endpoint for file uploads exists in the plugin (typically in the main plugin PHP file or a dedicated upload handler file)
    Affected if The gpxv_file_upload function is found in the plugin code and is registered as accessible to authenticated users
  4. Confirm subscriber-level users exist
    Navigate to WordPress admin > Users and review the list of users; check if any user has the 'Subscriber' role assigned, or query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'subscriber'
    Affected if At least one user account with the Subscriber role exists in the WordPress installation

You are affected if the GPX Viewer plugin is installed with version 2.2.9 or lower AND the gpxv_file_upload function is present and accessible to authenticated users (including subscribers).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of GPX Viewer (2.3.0+) which includes proper capability checks and file type validation. If no update is available, disable the plugin immediately to prevent exploitation.

Recommended fix Moderate confidence

GPX Viewer version 2.3.0 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the GPX Viewer plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org/plugins/gpx-viewer
  6. Verify the updated version is 2.3.0 or higher after updating

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

Have this fixed 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 help mitigating

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-2024-10629 — 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-10629 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