dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-49072

MEDIUM · 6.5 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 →
74/100
Remediation priority · Elevated
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 Broken Access Control in WooCommerce Anti-Fraud <= 7.2.6 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

Unauthenticated Broken Access Control vulnerability in WooCommerce Anti-Fraud plugin versions 7.2.6 and below allows attackers to access sensitive functionality or data without proper authentication, exploiting the lack of proper authorization checks on certain endpoints or actions.

MitigationUpdate WooCommerce Anti-Fraud to the latest patched version immediately. If no patch is available, consider disabling the plugin temporarily or restricting access to affected endpoints at the web server level until a fix is released.

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
Low

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

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. Check WooCommerce Anti-Fraud plugin version
    Log in to WordPress admin, navigate to Plugins > Installed Plugins, find WooCommerce Anti-Fraud, and note the version number displayed. Alternatively, inspect the plugin main file (usually includes/version.php or the primary plugin file) to read the Version header.
    Affected if The installed version is 7.2.6 or any version lower than 7.2.6
  2. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm that WooCommerce Anti-Fraud shows as 'Active' rather than 'Inactive' or 'Network Active'.
    Affected if The plugin is currently active and the version is 7.2.6 or below
  3. Confirm WordPress user authentication is not required for vulnerable actions
    Test access to common plugin endpoints (such as wp-admin/admin-ajax.php?action=... or custom REST API routes exposed by the plugin) using a browser or curl tool while logged out of WordPress. Check for unexpected 200 OK responses that should normally require admin privileges.
    Affected if Any sensitive plugin actions or data are accessible without being logged in, indicating broken access control is present

Your environment is affected if the WooCommerce Anti-Fraud plugin is active at version 7.2.6 or below and its sensitive endpoints are accessible without authentication.

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 WooCommerce Anti-Fraud to the latest patched version immediately. If no patch is available, consider disabling the plugin temporarily or restricting access to affected endpoints at the web server level until a fix is released.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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