CVE-2026-16145: Invisible Anti-Spam & CAPTCHA (WordPress plugin) · Cross-site Scripting
Affects Invisible Anti-Spam & CAPTCHA (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| matthiasnordwigInvisible Anti-Spam & CAPTCHA — reCAPTCHA Alternative for All Forms | Affected
| Fixed in– |
AI-suggested
Until a patch or official fix is available, users should consider disabling or restricting access to the vulnerable plugin or its ajax endpoints to prevent exploitation. Monitor vendor channels for updates and apply official fixes once released.
Description
The Invisible Anti-Spam & CAPTCHA — reCAPTCHA Alternative for All Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'action' parameter in all versions up to, and including, 5.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The stored payload is written by any unauthenticated admin-ajax.php request whose action value matches an entry in the plugin's explicit-actions list, which is auto-populated for common form builders at activation and requires no authentication gate to reach the save path.
References
- wordfence.com/threat-intel/vulnerabilities/id/ff1d2bd8-cc46-4763-8ba7-832b982ff56a?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/gdpr-compliant-recaptcha-for-all-forms/tags/5.0/includes/class-message-page.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/gdpr-compliant-recaptcha-for-all-forms/tags/5.0/includes/class-stamp.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/gdpr-compliant-recaptcha-for-all-forms/tags/5.0/includes/class-stamp.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3633500/gdpr-compliant-recaptcha-for-all-forms (opens in a new tab)