CVE-2025-31794
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 · uneditedMissing Authorization vulnerability in Web Ready Now WR Price List Manager For Woocommerce wr-price-list-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WR Price List Manager For Woocommerce: from n/a through <= 1.0.8.
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 confidenceThe WR Price List Manager For WooCommerce plugin (versions up to 1.0.8) contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This broken access control likely affects AJAX endpoints, admin pages, or API functionality within the plugin that fail to properly verify user capabilities before granting access to sensitive price list management features.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WR Price List Manager plugin is installedNavigate to WordPress admin > Plugins > Installed Plugins and locate 'WR Price List Manager For WooCommerce' in the listAffected if The plugin appears in the installed plugins list
-
Identify the installed plugin versionClick 'View details' on the WR Price List Manager plugin entry to display the version number, or check the plugin header in /wp-content/plugins/wr-price-list-manager/ directoryAffected if The installed version is 1.0.8 or lower
-
Confirm the plugin is activeCheck the status column in the Plugins list; the plugin must be active for the vulnerability to be exploitableAffected if The plugin status shows 'Active'
-
Inspect plugin AJAX endpoints for access controlExamine the plugin PHP files in /wp-content/plugins/wr-price-list-manager/ for wp_ajax_ and wp_ajax_nopriv_ action hooks; verify if capability checks (current_user_can, etc.) are present before sensitive operationsAffected if AJAX handlers exist without current_user_can() or similar capability validation
-
Review admin page access restrictionsCheck plugin PHP files for admin menu registration (add_menu_page, add_submenu_page) and whether capability parameters are set to restrict access to administrator or shop manager roles onlyAffected if Admin pages are registered without proper capability parameters or role-based restrictions
Your environment is affected if WR Price List Manager For WooCommerce is installed, active, and running version 1.0.8 or lower with AJAX endpoints or admin pages that lack capability verification checks.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest version of WR Price List Manager For WooCommerce when available; otherwise implement custom capability checks on all plugin endpoints and restrict access to trusted user roles only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31794 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31794 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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