dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-10392

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-31
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
The AI Power: Complete AI Pack plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'handle_image_upload' function in all versions up to, and including, 1.8.89. This makes it possible for unauthenticated attackers to upload 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 AI Power WordPress plugin has an arbitrary file upload vulnerability in the handle_image_upload function due to missing file type validation. Unauthenticated attackers can upload any file type, including executable PHP files, directly to the server, enabling potential remote code execution.

MitigationUpdate the AI Power plugin to version 1.8.90 or later which includes proper file type validation. Until updated, consider disabling the plugin or deploying a WAF rule to block suspicious file uploads.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 AI Power plugin is installed
    Log into WordPress admin, go to Plugins > Installed Plugins, and look for 'AI Power' (or 'AI Power - ChatGPT Content Writer & Generator' or similar) in the list
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In the Plugins list, click on the plugin name or view details to display the version number. Alternatively, check the plugin's main PHP file header or readme.txt for the Version field
    Affected if The version displayed is below 1.8.90 or the version cannot be determined
  3. Confirm the vulnerable function exists
    Examine the plugin files, typically in wp-content/plugins/ai-power or similar, locate the handle_image_upload function in the main plugin file or upload handler module
    Affected if The handle_image_upload function exists and lacks file type validation logic (missing mime type or extension checks)
  4. Test unauthenticated upload endpoint accessibility
    Send a POST request to the WordPress admin-ajax.php or the plugin's upload endpoint (commonly /wp-json/ai-power/upload or similar) without authentication, attempting to upload a harmless test file with an unexpected extension
    Affected if The upload request completes without requiring authentication or proper file type validation
  5. Check for suspicious uploaded files
    Inspect the wp-content/uploads/ai-power or similar upload directories for files with executable extensions (.php, .phtml, .js, .exe) that were not intentionally uploaded by administrators
    Affected if Unexpected executable files are present in the upload directories

The environment is affected if the AI Power plugin is installed with a version prior to 1.8.90 and the handle_image_upload function is present without proper file type validation.

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 the AI Power plugin to version 1.8.90 or later which includes proper file type validation. Until updated, consider disabling the plugin or deploying a WAF rule to block suspicious file uploads.

Recommended fix Moderate confidence

AI Power: Complete AI Pack version 1.8.90 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'AI Power: Complete AI Pack' plugin
  4. Check the current version number to confirm it is 1.8.89 or below
  5. If an update is available, click 'Update Now' to update to the latest version
  6. Alternatively, navigate to Dashboard > Updates and apply available updates
  7. After updating, verify the new version number reflects the patched release

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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