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

CVE-2025-3064

HIGH · 8.8 CVSS v3.1 Published 2025-04-08
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 WPFront User Role Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.2.1. This is due to missing or incorrect nonce validation on the whitelist_options() function. This makes it possible for unauthenticated attackers to update the default role option that can be leveraged for privilege escalation via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This is only exploitable on multisite instances.

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 WPFront User Role Editor plugin for WordPress has a CSRF vulnerability in the whitelist_options() function due to missing nonce validation. This allows unauthenticated attackers to forge requests that modify the default user role setting, potentially achieving privilege escalation on WordPress multisite installations.

MitigationUpdate to version 4.2.2 or later which includes proper nonce validation for the whitelist_options() function.

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. Locate WPFront User Role Editor plugin files
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wpfront-user-role-editor' or search for files containing 'WPFront User Role Editor' in the plugin headers
    Affected if The plugin folder or files are present in the plugins directory
  2. Identify the installed version
    Open the main plugin file (usually wpfront-user-role-editor.php) and locate the 'Version' header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entry
    Affected if The version number found is lower than 4.2.2 (e.g., 4.2.1, 4.2.0, earlier versions)
  3. Verify the plugin is active
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and confirm whether WPFront User Role Editor shows as 'Active'
    Affected if The plugin is active and the version is below 4.2.2
  4. Check for the vulnerable whitelist_options function
    Open the main plugin PHP file and search for the string 'whitelist_options' to confirm the function exists in the installed version
    Affected if The function 'whitelist_options' is present in the code (indicates the vulnerable code path exists)
  5. Determine if WordPress multisite is enabled
    Check wp-config.php for the line 'define( 'MULTISITE', true );' or inspect the network settings in the WordPress admin under Tools > Network (if multisite is active, the impact of this CSRF is higher)
    Affected if WordPress multisite is enabled and the plugin version is below 4.2.2

A user is affected if the WPFront User Role Editor plugin is installed, active, and running a version lower than 4.2.2, with the vulnerable whitelist_options function present in the code.

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 to version 4.2.2 or later which includes proper nonce validation for the whitelist_options() function.

Recommended fix Moderate confidence

Latest version higher than 4.2.1 (check wordpress.org for current release)

  1. 1. Navigate to the WordPress admin dashboard for the multisite installation.
  2. 2. Go to Plugins > Installed Plugins.
  3. 3. Locate the WPFront User Role Editor plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, manually download the latest version from wordpress.org/plugins/wpfront-user-role-editor/ and upload via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the new version is active and functioning correctly.

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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