dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-52379

CRITICAL · 10.0 CVSS v3.1 Published 2024-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Unrestricted Upload of File with Dangerous Type vulnerability in faizalbahasan kineticPay for WooCommerce kineticpay-for-woocommerce allows Upload a Web Shell to a Web Server.This issue affects kineticPay for WooCommerce: from n/a through <= 2.0.8.

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

The kineticPay for WooCommerce plugin (versions <= 2.0.8) contains an unrestricted file upload vulnerability that allows attackers to upload dangerous file types, specifically web shells, directly to the web server. This can lead to complete server compromise and remote code execution.

MitigationImmediately disable or remove the vulnerable kineticPay plugin until an official security patch is available. Conduct a forensic review of the server to check for any previously uploaded malicious files and restore from clean backups if compromise is detected.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Identify if kineticPay for WooCommerce plugin is installed
    Check the WordPress plugin directory for the kineticPay plugin folder, typically located at /wp-content/plugins/kineticpay-for-woocommerce/, or list installed WooCommerce payment gateway plugins.
    Affected if The kineticPay plugin folder exists in the WordPress plugins directory.
  2. Determine the installed plugin version
    Open the main plugin file (e.g., kineticpay-for-woocommerce.php) and locate the Version header in the plugin comment block, or check the WordPress admin plugins page for the installed version.
    Affected if The plugin version is present and matches any version known to contain this vulnerability (check against official plugin changelogs or security advisories).
  3. Inspect upload directories for suspicious files
    Review the wp-content/uploads/ directory (and any custom upload paths configured in WooCommerce) for unexpected .php, .phtml, or other executable files. Use: find /wp-content/uploads/ -name "*.php" -o -name "*.phtml" -o -name "*.php5"
    Affected if Any PHP or executable files exist in upload directories, especially files with names unrelated to legitimate uploads.
  4. Check web server PHP execution policy in upload folders
    Examine web server configuration (Apache .htaccess, Nginx config) for the upload directory. Look for directives that allow or block PHP execution in /wp-content/uploads/ or custom upload paths.
    Affected if PHP execution is permitted in upload directories (no RewriteRule or location block blocking .php files).

A user is affected if the kineticPay for WooCommerce plugin is installed with any vulnerable version, and the upload directories either contain suspicious PHP files or allow PHP execution.

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

Immediately disable or remove the vulnerable kineticPay plugin until an official security patch is available. Conduct a forensic review of the server to check for any previously uploaded malicious files and restore from clean backups if compromise is detected.

Recommended fix Moderate confidence

Latest available version of kineticPay for WooCommerce (version higher than 2.0.8)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate the 'kineticPay for WooCommerce' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update is shown in WordPress, manually download the latest version from the WordPress plugin repository or contact the vendor
  6. 6. Verify the update was successful by checking the plugin version after updating
  7. 7. Test that the payment functionality still works correctly after the update

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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