dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-68555

CRITICAL · 9.9 CVSS v3.1 Published 2026-03-05
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 zozothemes Nutrie nutrie allows Upload a Web Shell to a Web Server.This issue affects Nutrie: from n/a through < 2.0.1.

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 Nutrie theme before version 2.0.1 contains an unrestricted file upload vulnerability that allows attackers to upload dangerous file types (e.g., PHP scripts) to the web server. These uploaded files can be executed as web shells, enabling full remote code execution and complete server compromise.

MitigationUpdate Nutrie theme to version 2.0.1 or later. Additionally, implement strict file type validation (MIME type verification, extension whitelist, content-based magic number checking), store uploads outside the web root, and disable script execution in upload directories.

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. Locate the Nutrie theme installation
    Search the web server for theme files named 'nutrie' or 'Nutrie'. Check common paths like /wp-content/themes/nutrie/ for WordPress installations or /app/themes/nutrie/ for other PHP frameworks.
    Affected if The Nutrie theme folder exists on the server.
  2. Determine the installed Nutrie theme version
    Open the theme's style.css file or version.php file within the Nutrie theme directory and read the Version: header or $version variable.
    Affected if The version listed is below 2.0.1.
  3. Identify the file upload functionality
    Search the theme directory for upload-handling code (e.g., files containing 'move_uploaded_file', 'upload', or form handlers processing file inputs). Note the endpoint or PHP file handling uploads.
    Affected if The theme contains active upload handling code that accepts user-submitted files.
  4. Inspect upload directories for dangerous files
    Check directories where uploaded files are stored (look for 'uploads', 'upload', 'files', or similar folder names in the upload handler code). List all files with extensions like .php, .phtml, .php5, .phar, or .exe.
    Affected if Any PHP scripts or executable files exist in upload directories, indicating possible exploitation.

A user is affected if the Nutrie theme below version 2.0.1 is installed and its file upload functionality is accessible, or if suspicious PHP files are already present in upload folders.

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 Nutrie theme to version 2.0.1 or later. Additionally, implement strict file type validation (MIME type verification, extension whitelist, content-based magic number checking), store uploads outside the web root, and disable script execution in upload directories.

Recommended fix High confidence

Nutrie version 2.0.1 or later

  1. 1. Create a complete backup of the WordPress site including files and database
  2. 2. Download the Nutrie theme version 2.0.1 or later from the official zozothemes source
  3. 3. Navigate to WordPress admin > Appearance > Themes
  4. 4. Deactivate and delete the current vulnerable Nutrie theme
  5. 5. Install the updated Nutrie theme version 2.0.1 by uploading the new theme package
  6. 6. Activate the new Nutrie theme
  7. 7. Verify the upload functionality is working correctly and test file upload restrictions
  8. 8. Confirm the theme version in WordPress admin matches 2.0.1 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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