dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-12095

HIGH · 8.8 CVSS v3.1 Published 2025-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Simple Registration for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.5.8. This is due to missing nonce validation on the role requests admin page handler in the includes/display-role-admin.php file. This makes it possible for unauthenticated attackers to approve pending role requests and escalate user privileges via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Simple Registration for WooCommerce WordPress plugin. The role request approval handler in includes/display-role-admin.php lacks nonce validation, allowing unauthenticated attackers to forge administrative actions that approve pending role requests and escalate user privileges by tricking site administrators into clicking malicious links.

MitigationUpdate the plugin to version 1.5.9 or later which adds proper nonce validation to the role request admin handlers, or implement WAF rules to block forged requests to the vulnerable 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 plugin is installed
    Navigate to WordPress admin > Plugins and verify 'Simple Registration for WooCommerce' is listed as an active plugin
    Affected if Plugin is installed and active
  2. Check installed version
    In WordPress admin > Plugins, find 'Simple Registration for WooCommerce' and note the version number displayed under the plugin name. Compare this version against 1.5.9
    Affected if Version is lower than 1.5.9 or version number cannot be determined (plugin may be outdated)
  3. Verify vulnerable file exists
    Access your site via FTP or file manager and locate the file /wp-content/plugins/simple-registration-for-woocommerce/includes/display-role-admin.php. Check if this file exists on the server
    Affected if The file exists and plugin version is below 1.5.9
  4. Inspect role request functionality
    In WordPress admin, look for a role requests or registration requests menu item (typically under Users or a dedicated menu). Check if there are any pending role requests in the system
    Affected if There are pending role requests and the plugin is unpatched (attack targets approval of these requests)

You are affected if the Simple Registration for WooCommerce plugin is installed with a version lower than 1.5.9 and the vulnerable file includes/display-role-admin.php exists on your server.

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 plugin to version 1.5.9 or later which adds proper nonce validation to the role request admin handlers, or implement WAF rules to block forged requests to the vulnerable endpoint.

Recommended fix High confidence

Simple Registration for WooCommerce version 1.5.9 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Simple Registration for WooCommerce' in the plugin list
  4. Check if the current version is 1.5.8 or lower
  5. If vulnerable, click 'Update now' when an update is available, or manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the version number reflects the patch (version 1.5.9 or higher)
  7. Confirm the plugin functions correctly with WooCommerce

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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