dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-64374

CRITICAL · 9.9 CVSS v3.1 Published 2025-12-18
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 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 StylemixThemes Motors motors allows Using Malicious Files.This issue affects Motors: from n/a through <= 5.6.81.

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 Motors theme/plugin by StylemixThemes contains an unrestricted file upload vulnerability allowing attackers to upload dangerous file types (e.g., malicious PHP scripts). With a CVSS 9.9, this critical flaw likely enables remote code execution by bypassing file type validation during the upload process.

MitigationImplement strict allowlist-based file validation (checking both MIME type and file extension), sanitize filenames, and store uploads outside the web root or with executable permissions removed to prevent RCE.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Motors theme is installed
    Check your WordPress wp-content/themes directory for the 'motors' theme folder. You can also list installed themes via WordPress admin under Appearance > Themes or by querying the wp_options table for 'template' or 'stylesheet' values containing 'motors'.
    Affected if The motors theme folder exists in your WordPress themes directory.
  2. Identify the installed theme version
    Locate the style.css file within the motors theme folder and read the 'Version:' header. Alternatively, check version.php in the theme root directory for a version variable. Compare this version number against the vendor's patched version release notes.
    Affected if You cannot determine the version or the version is older than the latest patched release.
  3. Verify file upload functionality exists
    Check if the theme's car listing or inventory submission forms include file upload fields (typically for vehicle images or documents). Inspect the form HTML for <input type='file'> elements and identify the upload handler endpoint.
    Affected if File upload forms exist and are accessible without admin authentication.
  4. Inspect server-side file validation
    Examine the PHP file handling the uploads (commonly in includes/admin or templates directories). Look for $_FILES processing code and check if it validates file MIME types, extensions, or uses functions like wp_check_filetype. Search for any hardcoded allowlist or denylist of permitted file types.
    Affected if No server-side file type/extension validation is performed before moving uploaded files.
  5. Check upload directory configuration
    Review the wp-config.php and theme settings to identify where uploaded files are stored. Verify if uploads are placed in the default wp-content/uploads directory which is web-accessible. Also check for .htaccess or nginx config in upload directories that should block script execution.
    Affected if Uploaded files are stored in web-accessible directories without script execution disabled.

Your environment is affected if the Motors theme is installed with an unpatched version and includes accessible file upload functionality without proper server-side 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based file validation (checking both MIME type and file extension), sanitize filenames, and store uploads outside the web root or with executable permissions removed to prevent RCE.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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