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

CVE-2025-1764

HIGH · 7.5 CVSS v3.1 Published 2025-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 LoginPress | wp-login Custom Login Page Customizer plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.3.1. This is due to missing or incorrect nonce validation on the 'custom_plugin_set_option' function. This makes it possible for unauthenticated attackers to update arbitrary options on the WordPress site via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site. The 'WPBRIGADE_SDK__DEV_MODE' constant must be set to 'true' to exploit the vulnerability.

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 LoginPress WordPress plugin has a CSRF vulnerability in the custom_plugin_set_option function due to missing nonce validation. Attackers can forge administrator requests to update arbitrary WordPress options, specifically enabling user registration and setting the default role to administrator to create admin accounts. Exploitation requires the WPBRIGADE_SDK__DEV_MODE constant to be set to true.

MitigationUpdate LoginPress to the latest version and ensure the WPBRIGADE_SDK__DEV_MODE constant is not set to true in any configuration files.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 LoginPress plugin is installed
    Check the wp-content/plugins/ directory for the loginpress folder, or query the WordPress plugins API endpoint /wp-json/wp/v2/plugins?search=loginpress
    Affected if LoginPress plugin files are present in the WordPress installation
  2. Identify installed LoginPress version
    Open the main plugin file (e.g., wp-content/plugins/loginpress/loginpress.php) and locate the 'Version' header in the plugin comment block, or check the WordPress plugins admin page
    Affected if Version cannot be determined or is within an affected range prior to the patched release
  3. Check for WPBRIGADE_SDK__DEV_MODE constant
    Search wp-config.php, wp-content/debug.log, theme functions.php, and any must-use plugins for the line: define('WPBRIGADE_SDK__DEV_MODE', true);
    Affected if The constant WPBRIGADE_SDK__DEV_MODE is defined and set to true in any configuration file
  4. Inspect custom_plugin_set_option accessibility
    Review the LoginPress plugin file containing the custom_plugin_set_option function (typically in includes/class-loginpress-sdk.php or similar) to confirm it processes requests without nonce verification
    Affected if The function lacks nonce validation logic (search for 'nonce' or 'wp_verify_nonce' in that function)
  5. Verify current user registration settings
    In WordPress admin, go to Settings > General and check 'Anyone can register' setting, or query the database: SELECT option_value FROM wp_options WHERE option_name IN ('users_can_register', 'default_role')
    Affected if User registration is enabled and default_role is set to administrator (this indicates potential exploitation but the root cause is step 3)

A user is affected if LoginPress is installed with the WPBRIGADE_SDK__DEV_MODE constant set to true, enabling the CSRF vector to modify WordPress settings.

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 LoginPress to the latest version and ensure the WPBRIGADE_SDK__DEV_MODE constant is not set to true in any configuration files.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version > 3.3.1)

  1. Check if the 'WPBRIGADE_SDK__DEV_MODE' constant is set to 'true' in any WordPress configuration files (wp-config.php, theme functions.php, or plugin files) and set it to 'false' if not needed for development
  2. Update the LoginPress plugin to the latest available version from the WordPress plugin repository
  3. Verify the update was successful by checking the plugin version in WordPress admin under Plugins > Installed Plugins
  4. Review any recently created administrative user accounts for suspicious activity
  5. Consider enabling WordPressnonce tokens for admin actions as an additional hardening measure

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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