dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-47463

HIGH · 7.1 CVSS v3.1 Published 2025-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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
Missing Authorization vulnerability in Fahad Mahmood Stock Locations for WooCommerce stock-locations-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Stock Locations for WooCommerce: from n/a through <= 2.8.6.

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

Missing Authorization vulnerability in the Stock Locations for WooCommerce plugin allows attackers to bypass access control checks due to incorrectly configured security levels, potentially enabling unauthorized access to sensitive stock location data and inventory management functionality.

MitigationUpdate Stock Locations for WooCommerce to the latest version; if unavailable, review and enforce proper capability checks and nonce validation on all admin ajax and front-end endpoints within the plugin.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 plugin installation and version
    In WordPress admin, go to Plugins > Instored Plugins and locate 'Stock Locations for WooCommerce' or check the plugin header file /wp-content/plugins/stock-locations-for-woocommerce/stock-locations-for-woocommerce.php for the Version defined constant
    Affected if The plugin is installed and the version cannot be confirmed as patched against this authorization bypass
  2. Identify accessible AJAX endpoints
    Review the plugin directory /wp-content/plugins/stock-locations-for-woocommerce/ for files handling admin-ajax.php or front-end AJAX requests, typically in includes/ or ajax/ folders. List all registered action hooks using 'add_action' for 'wp_ajax_' and 'wp_ajax_nopriv_'
    Affected if The plugin registers AJAX endpoints without capability checks or with 'wp_ajax_nopriv_' hooks allowing unauthenticated access to inventory functions
  3. Test unauthorized access to stock location data
    Send a direct HTTP POST request to /wp-admin/admin-ajax.php with a known plugin action (such as 'slw_get_locations' or similar) without including valid authentication cookies or nonce tokens, then observe if the response returns sensitive stock location or inventory data
    Affected if The endpoint returns stock location data, inventory levels, or warehouse details without requiring login or proper capability verification
  4. Verify capability checks on admin functions
    Examine the plugin PHP source code for current_user_can() or wp_get_current_user() calls around sensitive functions that handle stock location creation, editing, or deletion. Check if these checks are consistently applied before executing database operations
    Affected if Sensitive inventory management functions lack proper 'current_user_can()' capability gates or have conditional checks that can be bypassed
  5. Inspect nonce validation on endpoints
    Search the plugin code for 'wp_verify_nonce' or 'check_ajax_referer' calls on AJAX handlers. Determine if nonces are required for each state-changing operation (add, edit, delete stock locations) and whether they are properly validated before processing
    Affected if AJAX endpoints that modify stock data do not validate nonces or have nonce checks that can be circumvented

The environment is affected if the Stock Locations for WooCommerce plugin is installed and its AJAX or front-end endpoints expose stock location or inventory data without requiring authentication or proper capability verification.

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 Stock Locations for WooCommerce to the latest version; if unavailable, review and enforce proper capability checks and nonce validation on all admin ajax and front-end endpoints within the plugin.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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