Findings

Vulnerability · CVE-2026-2374

The Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the superglobal in all versions up to, and including, 1.8.0.

Published May 28, 2026 · corrected/updated Jun 17, 2026 · evidence confidence medium

The Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the superglobal in all versions up to, and including, 1.8.0. This is due to the function storing the unsanitized output of in the WordPress option when a login attempt is made from a non-standard login page (e.g., xmlrpc.php). The 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.

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2026-2374 is a high public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected version ranges have not been ingested yet. Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: CVSS 7.2, EPSS 0.3%. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-79. Sources contributing to this record: epss, nvd. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.

  • Patch and remediation

    No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 28, 2026 · NIST NVD

    Detected

    The Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the superglobal in all versions up to, and including, 1.8.0. This is due to the function storing the unsanitized output of in the WordPress option when a login attempt is made from a non-standard login page (e.g., xmlrpc.php). The function then echoes this stored value directly into the admin dashb

  2. Jun 17, 2026 · NIST NVD

    Updated

    The Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the superglobal in all versions up to, and including, 1.8.0. This is due to the function storing the unsanitized output of in the WordPress option when a login attempt is made from a non-standard login page (e.g., xmlrpc.php). The function then echoes this stored value directly into the admin dashb

Sources

  • FIRST EPSSExploitation probabilityCVE-2026-2374

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDVulnerability recordCVE-2026-2374

    The Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the superglobal in all versions up to, and including, 1.8.0. This is due to the function storing the unsanitized output of `basename($_SERV

    nvd.nist.gov

References