dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-2374

HIGH · 7.2 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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 Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `$_SERVER['PHP_SELF']` superglobal in all versions up to, and including, 1.8.0. This is due to the `authenticate()` function storing the unsanitized output of `basename($_SERVER['PHP_SELF'])` in the `login_nocaptcha_error` WordPress option when a login attempt is made from a non-standard login page (e.g., xmlrpc.php). The `admin_notices()` function then echoes this stored value directly into the admin dashboard HTML without escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator with a whitelisted IP address visits the WordPress dashboard within 30 seconds of the attack.

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 Login No Captcha reCAPTCHA plugin for WordPress stores unsanitized basename($_SERVER['PHP_SELF']) input in the login_nocaptcha_error option via the authenticate() function when login attempts occur from non-standard endpoints like xmlrpc.php. The admin_notices() function then echoes this stored value directly into the admin dashboard HTML without escaping, allowing stored XSS injection that executes when administrators visit the dashboard.

MitigationSanitize the basename($_SERVER['PHP_SELF']) value before storing it and ensure all output of the login_nocaptcha_error option is properly escaped in the admin_notices() 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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

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. Identify if Login No Captcha reCAPTCHA plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Login No Captcha reCAPTCHA' or check the wp-content/plugins directory for a folder named 'login-nocaptcha' or similar. Also query the wp_options table for rows where option_name contains 'login_nocaptcha'.
    Affected if The plugin is not installed or not present in the WordPress plugins directory and database options.
  2. Determine the installed plugin version
    Open the main plugin file (usually login-nocaptcha.php or similar in the plugin folder) and look for the version comment at the top of the file. Compare this version against the known affected version range if provided by the vendor security advisory.
    Affected if The installed version falls within the range that contains the unsanitized basename() storage vulnerability.
  3. Inspect the login_nocaptcha_error option in the database
    Query the wp_options table: SELECT * FROM wp_options WHERE option_name = 'login_nocaptcha_error'; Examine the option_value column. This value should contain only the basename of the PHP_SELF from legitimate login attempts.
    Affected if The option_value contains unexpected content such as HTML script tags, JavaScript event handlers, or other suspicious payloads that do not match a valid basename of a PHP endpoint.
  4. Review the admin_notices function for missing output escaping
    Locate the admin_notices() function in the plugin source code. Check if the login_nocaptcha_error option is output using a function like echo get_option('login_nocaptcha_error') without being passed through esc_html() or similar escaping functions first.
    Affected if The admin_notices function outputs the login_nocaptcha_error option value directly without escaping, allowing stored XSS to execute when an administrator loads the admin dashboard.
  5. Review the authenticate function for missing input sanitization
    Locate the authenticate() function in the plugin source code. Check if basename($_SERVER['PHP_SELF']) is stored directly into the login_nocaptcha_error option without being sanitized (e.g., without sanitize_text_field or similar).
    Affected if The authenticate function stores the basename($_SERVER['PHP_SELF']) value without sanitization, enabling injection of arbitrary content into the option.

A user is affected if the Login No Captcha reCAPTCHA plugin is installed with a vulnerable version and both the authenticate() function stores unsanitized basename($_SERVER['PHP_SELF']) while the admin_notices() function outputs the login_nocaptcha_error option without escaping.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Sanitize the basename($_SERVER['PHP_SELF']) value before storing it and ensure all output of the login_nocaptcha_error option is properly escaped in the admin_notices() function.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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