dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-0845

HIGH · 7.2 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
The WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the 'WCFM_Settings_Controller::processing' function in all versions up to, and including, 6.7.24. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 WCFM plugin for WooCommerce has a broken access control vulnerability in the WCFM_Settings_Controller::processing function, which lacks a proper capability check. This allows authenticated users with Shop Manager role or higher to modify arbitrary WordPress options. Attackers can change the default registration role to Administrator and enable user registration, enabling complete site takeover.

MitigationUpdate the plugin to the latest version once available. In the interim, audit user roles and consider restricting the Shop Manager role or implementing additional access controls on the affected endpoints.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm WCFM plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'WCFM - WooCommerce Frontend Manager' or check the plugin files for version information in the main plugin file header
    Affected if WCFM plugin is installed and active
  2. Identify installed WCFM version
    View the plugin version in the Plugins list or read the main plugin file (usually wcfm.php) to find the Version: header
    Affected if Version is within the affected range and cannot be determined as patched
  3. Verify Shop Manager role exists
    Navigate to Users > Users in WordPress admin and filter or check for users with 'Shop Manager' role, or use a role editor plugin to list all available roles
    Affected if Shop Manager role exists and has active user accounts
  4. Check WordPress user registration settings
    Go to Settings > General in WordPress admin and check if 'Membership: Anyone can register' is enabled, noting the default role setting
    Affected if User registration is enabled with a privileged role as default (such as Administrator or Editor)
  5. Inspect endpoint access control
    Review the WCFM_Settings_Controller::processing function in the plugin code to verify capability checks exist before processing settings changes, or test the settings endpoint with a limited user account
    Affected if The processing function lacks proper capability verification (such as 'manage_options' check)

Your environment is affected if WCFM plugin is installed, the installed version falls within the vulnerable range, and a user with Shop Manager role or lower can access the unprotected settings endpoint to modify WordPress options.

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 the plugin to the latest version once available. In the interim, audit user roles and consider restricting the Shop Manager role or implementing additional access controls on the affected endpoints.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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