dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-3605

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The Frontend Login and Registration Blocks plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.1.1. This is due to the plugin not properly validating a user's identity prior to updating their details like email via the flr_blocks_user_settings_handle_ajax_callback() function. This makes it possible for unauthenticated attackers to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.

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 Frontend Login and Registration Blocks WordPress plugin (versions up to 1.1.1) lacks proper identity validation in the flr_blocks_user_settings_handle_ajax_callback() function, allowing unauthenticated attackers to change any user's email address. Attackers can then trigger a WordPress password reset for that email and take over the account, including administrator accounts.

MitigationUpdate to version 1.1.2 or later which includes proper user authentication checks. Until then, consider disabling the plugin or restricting access to the vulnerable AJAX endpoint via server-side rules.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 the plugin and determine its version
    Check the WordPress plugin directory: navigate to /wp-content/plugins/frontend-login-and-registration-blocks/ and open the main PHP file (usually named similar to the plugin slug or index.php) to read the Version header in the plugin comment block. Alternatively, in WordPress admin, go to Plugins > Installed Plugins and locate 'Frontend Login and Registration Blocks' to see the version number.
    Affected if The plugin is installed and the version displayed is 1.1.1 or lower (any version up to and including 1.1.1).
  2. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify whether 'Frontend Login and Registration Blocks' shows as 'Active' under the plugin status, or query the wp_options table for the active_plugins option.
    Affected if The plugin is active on the site.
  3. Verify AJAX endpoint is accessible
    Check if the flr_blocks AJAX endpoint is publicly accessible by inspecting the plugin code for the action hook (usually wp_ajax_nopriv_ or wp_ajax_ actions registering 'flr_blocks_user_settings_handle_ajax_callback') or by reviewing server access logs for POST requests to /wp-admin/admin-ajax.php with the flr_blocks action parameter.
    Affected if The vulnerable AJAX callback is registered for unauthenticated users (wp_ajax_nopriv_ hook exists).

You are affected if the Frontend Login and Registration Blocks plugin is installed at version 1.1.1 or lower and is currently active, with the AJAX callback accessible to unauthenticated users.

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 1.1.2 or later which includes proper user authentication checks. Until then, consider disabling the plugin or restricting access to the vulnerable AJAX endpoint via server-side rules.

Recommended fix Moderate confidence

Latest version of Frontend Login and Registration Blocks plugin (version higher than 1.1.1)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate the 'Frontend Login and Registration Blocks' plugin.
  4. 4. Check if an update is available. If so, update to the latest version.
  5. 5. Verify the update was successful by confirming the new version number.
  6. 6. Review user accounts, especially administrator accounts, for any unauthorized changes.
  7. 7. Consider force-resetting passwords for all administrator accounts as a precautionary measure.
  8. 8. Monitor the site for any suspicious activity following the update.

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-3605 — 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-3605 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