The SEOJuice WordPress plugin before 2.12.0 does not correctly restrict a REST API authentication filter, disabling
Source GCVE Database
Not known to be exploited : upgrade to 2.12.0 soon.
Data as of 14 Nov 2026, 10:03 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.12.0
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Nov 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
Upgrade SEOJuice (WordPress plugin) to 2.12.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SEOJuice | Affected
| Fixed in
|
AI-suggested
Upgrade the SEOJuice WordPress plugin to version 2.12.0 or later, where this vulnerability is fixed. No other mitigation is indicated in the provided data. Patch status is not explicitly confirmed in the input, but the fixed version is identified as 2.12.0, so updating to this version or later remediates the issue.
Description
The SEOJuice WordPress plugin versions before 2.12.0 have a vulnerability where the REST API authentication filter is not properly restricted. This flaw disables WordPress's REST nonce protection site-wide, allowing unauthenticated attackers to perform any cookie-authenticated REST action. An attacker can exploit this by tricking a logged-in administrator into visiting a crafted page, enabling actions such as creating a new administrator account via CSRF.