dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-10516

HIGH · 8.1 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Swift Performance Lite plugin for WordPress is vulnerable to Local PHP File Inclusion in all versions up to, and including, 2.3.7.1 via the 'ajaxify' function. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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 Swift Performance Lite WordPress plugin versions up to 2.3.7.1 contain a Local PHP File Inclusion vulnerability in the ajaxify function, allowing unauthenticated attackers to include and execute arbitrary files on the server. This enables execution of any PHP code present in uploaded files (including commonly 'safe' file types like images), potentially leading to complete system compromise.

MitigationUpgrade to version 2.3.7.2 or later; if immediate patching is not possible, disable the plugin or restrict access to the ajaxify endpoint via web server configuration until a patch can be applied.

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Verify Swift Performance Lite plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'swift-performance' or 'swift-performance-lite', or query the wp_options table for the active_plugins option
    Affected if The plugin folder exists in wp-content/plugins/
  2. Determine installed plugin version
    Open the main plugin file (usually swift-performance.php or swift-performance-lite.php) and locate the version defined in the plugin header comment, or query the wp_options table for the option_name containing 'plugin_version'
    Affected if The version string is 2.3.7.1 or lower
  3. Confirm the ajaxify feature is enabled
    Check the plugin settings via WordPress admin, or inspect the database wp_options table for options related to 'ajaxify' that may be set to enabled (value may be 1, 'true', or 'enabled')
    Affected if The ajaxify functionality is turned on in plugin settings or database options
  4. Check for the vulnerable ajaxify endpoint
    Probe the endpoint at /wp-admin/admin-ajax.php?action=swift_performance_ajaxify or similar, using a tool like curl to see if the endpoint responds (note: actual parameter names may vary)
    Affected if The ajaxify endpoint responds and appears to process file inclusion parameters

A user is affected if Swift Performance Lite version 2.3.7.1 or lower is installed with the ajaxify feature enabled, allowing the file inclusion endpoint to be accessible.

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

Upgrade to version 2.3.7.2 or later; if immediate patching is not possible, disable the plugin or restrict access to the ajaxify endpoint via web server configuration until a patch can be applied.

Recommended fix High confidence

2.3.7.2 or latest version available in the WordPress plugin repository

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Swift Performance Lite and click 'Update Now'
  4. Alternatively, download the latest version from wordpress.org/plugins/swift-performance and upload via FTP or WordPress plugin upload

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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