dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-54807

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-17
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
Unauthenticated Privilege Escalation in Registration Form for WooCommerce <= 1.0.9 versions.

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

An unauthenticated privilege escalation vulnerability exists in the Registration Form for WooCommerce plugin versions 1.0.9 and below. Attackers can exploit the registration form to gain elevated privileges (likely administrator access) without needing valid credentials, potentially compromising the entire WooCommerce store and WordPress installation.

MitigationUpdate the Registration Form for WooCommerce plugin to the latest version. If no patched version is available, remove the plugin until a fix is released, as the unauthenticated nature of this vulnerability poses immediate risk.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 plugin installation and version
    Check the installed version of the Registration Form for WooCommerce plugin. In WordPress admin, go to Plugins > Installed Plugins and look for Registration Form for WooCommerce. Alternatively, inspect the main plugin file (registration-form-for-woocommerce.php) in wp-content/plugins/ and look for the 'Version' header in the plugin comments. Or run: grep -i 'Version:' wp-content/plugins/registration-form-for-woocommerce/*.php
    Affected if The installed version is 1.0.9 or lower, or if the version cannot be determined (plugin is present but version header is missing/corrupt).
  2. Confirm WordPress user registration is enabled
    Navigate to WordPress Dashboard > Settings > General > 'Membership' section. Verify if the checkbox labeled 'Anyone can register' is checked. If using a config file, search for 'users_can_register' in wp-config.php set to true.
    Affected if The 'Anyone can register' option is enabled in WordPress settings, making the registration form accessible to unauthenticated users.
  3. Check if the plugin registration form is active
    Locate the plugin settings page in WordPress admin under WooCommerce > Registration Form, or a dedicated settings page for this plugin. Verify whether the registration form functionality is turned ON or enabled.
    Affected if The plugin's registration form is enabled and publicly accessible (no login required to access it).
  4. Inspect for unauthorized administrator accounts
    Go to WordPress Dashboard > Users and review all accounts with the 'Administrator' role. Look for unfamiliar admin accounts that were not created by known administrators. Check user registration dates in the database: SELECT user_login, user_registered FROM wp_users WHERE ID IN (SELECT user_id FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%administrator%');
    Affected if New or unexpected administrator accounts exist in the database that were not created by legitimate site administrators.

If the Registration Form for WooCommerce plugin version 1.0.9 or below is installed with the registration form enabled and WordPress user registration is open to anyone, the environment is vulnerable to unauthenticated privilege escalation.

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 Registration Form for WooCommerce plugin to the latest version. If no patched version is available, remove the plugin until a fix is released, as the unauthenticated nature of this vulnerability poses immediate risk.

Recommended fix Moderate confidence

Latest version of Registration Form for WooCommerce (greater than 1.0.9)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Registration Form for WooCommerce'
  4. Check the current version number to confirm it is 1.0.9 or lower
  5. If vulnerable, click 'Update Now' if an update is available, or download the latest version from the WordPress plugin repository
  6. After updating, verify the new version number in the plugins list
  7. Test the registration functionality to ensure the plugin still works correctly
Caveat Minor: Review any changes to default registration settings after upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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