dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-60207

CRITICAL · 10.0 CVSS v3.1 Published 2025-11-06
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 Addify Custom User Registration Fields for WooCommerce user-registration-plugin-for-woocommerce allows Upload a Web Shell to a Web Server.This issue affects Custom User Registration Fields for WooCommerce: from n/a through <= 2.1.2.

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 Addify Custom User Registration Fields for WooCommerce plugin contains an unrestricted file upload vulnerability that allows authenticated or possibly unauthenticated attackers to upload executable files (PHP scripts) through the user registration fields functionality. These uploaded files can be executed as web shells, providing complete remote code execution on the server.

MitigationUpdate to the latest patched version of the plugin immediately. If no patch is available, disable and remove the plugin. Conduct a forensic investigation to check for any existing web shells or backdoors already uploaded to the server.

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. Confirm the Addify Custom User Registration Fields plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Addify Custom User Registration Fields for WooCommerce' in the installed plugins list, or inspect the wp-content/plugins directory for a folder containing 'addify-custom-user-registration'
    Affected if The plugin appears in the installed plugins list or filesystem
  2. Determine the installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view its details and version number, or read the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if The version number cannot be determined or is lower than the patched version published by the vendor
  3. Inspect upload directories for suspicious PHP files
    Examine the wp-content/uploads directory and any custom upload paths configured in the plugin. Look for files with .php extensions, especially those with names like shell.php, backdoor.php, or random alphanumeric strings ending in .php
    Affected if Any PHP files exist in upload directories that were not intentionally placed there by administrators
  4. Check for recently created or modified PHP files in web root
    Use the command 'find /var/www/html -name "*.php" -mtime -30' (adjust path to match web root) to list PHP files modified within the last 30 days, then review each for suspicious code patterns such as base64_decode, eval, shell_exec, or system calls
    Affected if Unexpected PHP files exist that were created recently and contain suspicious encoding or system command functions
  5. Review web server access logs for file upload patterns
    Search access logs (typically in /var/log/nginx or /var/log/apache2) for POST requests to /wp-content/uploads/ containing .php file extensions, or requests to the plugin registration endpoint that include file upload parameters
    Affected if POST requests from unknown sources are logged uploading .php files to upload directories

A user is affected if the Addify Custom User Registration Fields plugin is installed AND the version is below the patched version released by Addify, OR if unauthorized PHP files exist in upload directories indicating exploitation.

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

Update to the latest patched version of the plugin immediately. If no patch is available, disable and remove the plugin. Conduct a forensic investigation to check for any existing web shells or backdoors already uploaded to the server.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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