CVE-2026-85117: Contact Form 7 Captcha (WordPress plugin) · Injection
Affects Contact Form 7 Captcha (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.1.9 when convenient.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-09-09.
- Patch
- Available – fixed in 0.1.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade Contact Form 7 Captcha (WordPress plugin) to 0.1.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Contact Form 7 Captcha | Affected
| Fixed in
|
AI-suggested
Upgrade the Contact Form 7 Captcha plugin to version 0.1.9 or later, where this vulnerability is fixed. No other mitigation is required as the patch fully addresses the issue.
Description
Contact Form 7 Captcha WordPress plugin versions 0.1.7 and 0.1.8 contain a vulnerability where the shortcode parser processes the entire rendered form including user-submitted values. This allows unauthenticated users to execute arbitrary shortcodes registered on the site. The issue is fixed in version 0.1.9.