dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-60211

HIGH · 8.8 CVSS v3.1 Published 2025-10-22
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
Incorrect Privilege Assignment vulnerability in extendons WooCommerce Registration Fields Plugin - Custom Signup Fields extendons-registration-fields allows Privilege Escalation.This issue affects WooCommerce Registration Fields Plugin - Custom Signup Fields: from n/a through <= 3.2.3.

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

A privilege escalation vulnerability in the extendons WooCommerce Registration Fields plugin allows authenticated users to gain administrative privileges through improper role assignment during the registration process. The plugin incorrectly assigns user roles, likely allowing manipulation of registration parameters to bypass intended access controls.

MitigationUpdate to a patched version of the plugin when available. Until then, disable or restrict user registration functionality, and audit existing user accounts for unauthorized administrative access.

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. Identify if the extendons plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'extendons WooCommerce Registration Fields' or check the plugin files in /wp-content/plugins/ for a folder matching that name
    Affected if The plugin is present and active on the WordPress site
  2. Check the installed plugin version
    In WordPress admin > Plugins, find the plugin and view the version number under the plugin name, or read the main plugin PHP file header for the Version field
    Affected if The version is unpatched and falls within the vulnerable range (verify against any released patch notes from extendons)
  3. Verify WooCommerce user registration is enabled
    Go to WooCommerce > Settings > Account and Privacy, or check WordPress > Settings > General for 'Anyone can register' and ensure the default role is not set to Administrator
    Affected if User registration is enabled and allows role selection or default role assignment through the plugin
  4. Inspect the plugin role assignment configuration
    Look in WooCommerce > Registration Fields (or the plugin settings panel) for any fields that allow users to select or influence their role during registration; check if the role field can be manipulated or is missing proper validation
    Affected if A role selection field exists in registration forms or the plugin allows overriding the default role without proper server-side validation
  5. Audit existing user accounts for unauthorized administrators
    Go to WordPress Users and review all accounts with Administrator role; check user registration dates and email addresses for anomalies; look for accounts created around the time the plugin was active
    Affected if There are admin accounts you did not create, or admin accounts with suspicious email patterns or registration dates

Your site is affected if the extendons WooCommerce Registration Fields plugin is installed with user registration enabled and the plugin allows role manipulation during registration, or if unauthorized admin accounts exist.

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 a patched version of the plugin when available. Until then, disable or restrict user registration functionality, and audit existing user accounts for unauthorized administrative access.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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