dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-7847

HIGH · 8.8 CVSS v3.1 Published 2025-07-31
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 AI Engine plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the rest_simpleFileUpload() function in versions 2.9.3 and 2.9.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server when the REST API is enabled, 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 Engine WordPress plugin versions 2.9.3-2.9.4 lacks proper file type validation in the rest_simpleFileUpload() function, allowing authenticated users with Subscriber-level access or higher to upload arbitrary files via the REST API, potentially achieving remote code execution.

MitigationUpdate the AI Engine plugin to the latest version immediately; alternatively, disable the REST API endpoint or restrict subscriber-level users until a patch is 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
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. Verify AI Engine plugin is installed
    Check the WordPress plugin directory for the AI Engine plugin, or list active plugins via wp-cli: wp plugin list --name='ai-engine'
    Affected if AI Engine plugin is present in the WordPress installation
  2. Check the installed AI Engine version
    View the plugin header in wp-content/plugins/ai-engine/ai-engine.php, or run: wp plugin get ai-engine --field=version
    Affected if Version is 2.9.3 or 2.9.4 (exact match to affected versions)
  3. Confirm REST API is enabled
    Check WordPress general settings or inspect the REST API endpoint /wp-json/ returns a valid response; verify no firewall or plugin is blocking REST API access
    Affected if REST API is accessible and returns HTTP 200 OK responses
  4. Verify subscriber-level users can access file upload
    Test REST API endpoint /wp-json/ai-engine/v1/simple-file-upload with a subscriber account, or inspect the rest_simpleFileUpload() function capability checks in the plugin code
    Affected if Subscriber-role users have permission to access the file upload REST endpoint

User is affected if AI Engine version is exactly 2.9.3 or 2.9.4 AND the REST API is enabled AND subscriber-level accounts can access the file upload endpoint.

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 Engine plugin to the latest version immediately; alternatively, disable the REST API endpoint or restrict subscriber-level users until a patch is applied.

Recommended fix Moderate confidence

AI Engine version 2.9.5 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'AI Engine' plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest patched version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/ai-engine/ and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running the patched version under Plugins > Installed Plugins

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-2025-7847 — 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-2025-7847 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