dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-12994

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.7.27. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to inject arbitrary reply content into any store inquiry, overwrite the main inquiry record in wp_wcfm_enquiries, and trigger unsolicited notification emails to customers and vendors. Unlike sibling controller branches (wcfm-enquiry and wcfm-enquiry-manage), the wcfm-my-account-enquiry-manage branch performs no is_user_logged_in() or current_user_can() check, and the nonce that serves as the sole barrier is embedded into every public page load without any login gate.

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 an authorization bypass in the wcfm-my-account-enquiry-manage endpoint. The vulnerability exists because this endpoint lacks is_user_logged_in() and current_user_can() checks, relying only on a nonce that is publicly exposed on all page loads. This allows unauthenticated attackers to inject replies into any store inquiry, modify inquiry records in the wp_wcfm_enquiries table, and trigger unwanted notification emails.

MitigationUpdate the WCFM – Frontend Manager for WooCommerce plugin to version 6.7.28 or later. Until then, disable the plugin or implement web application firewall rules to block unauthenticated access to the wcfm-my-account-enquiry-manage endpoint.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 WCFM plugin is installed
    Check for the presence of the WCFM plugin directory in wp-content/plugins (typically named 'wc-frontend-manager' or similar). Look for the main plugin file and examine the plugin header for version information.
    Affected if The WCFM plugin is found installed on the WordPress site
  2. Determine installed WCFM version
    Locate the main plugin file (usually wcfm.php or class-wcfm.php) and read the Version field from the plugin header comment. Compare this version number against 6.7.28.
    Affected if Installed version is lower than 6.7.28
  3. Test wcfm-my-account-enquiry-manage endpoint accessibility
    Send a GET or POST request to the wcfm-my-account-enquiry-manage endpoint (typically at /?wcfm-my-account-enquiry-manage=some_id or via AJAX endpoint) without providing any authentication cookies or credentials. Observe if the server returns a successful response rather than a redirect to login.
    Affected if The endpoint responds to unauthenticated requests without requiring login
  4. Verify nonce is exposed on public pages
    View the HTML source of any public-facing page on the site and search for the string 'wcfm_enquiry_nonce' or similar nonce fields related to the enquiry functionality. If found in page source visible to unauthenticated visitors, the nonce is publicly exposed.
    Affected if The enquiry-related nonce is present in HTML source accessible to unauthenticated visitors

A site is affected if the WCFM plugin version is below 6.7.28 and the wcfm-my-account-enquiry-manage endpoint accepts unauthenticated requests, allowing attackers to manipulate inquiry records without login.

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 WCFM – Frontend Manager for WooCommerce plugin to version 6.7.28 or later. Until then, disable the plugin or implement web application firewall rules to block unauthenticated access to the wcfm-my-account-enquiry-manage endpoint.

Recommended fix Moderate confidence

WCFM – Frontend Manager for WooCommerce version 6.7.28 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WCFM – Frontend Manager for WooCommerce' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin version is 6.7.28 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.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-2026-12994 — 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-12994 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