The ThinkRank SEO WordPress plugin before 2.21.4 does not ensure that the settings section a request acts on is the
Source GCVE Database
Not known to be exploited : upgrade to 2.21.4 soon.
Data as of 22 Nov 2026, 07:27 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.21.4
Exploitation evidence
Disclosed: evidence found.
CVE published 22 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 21 Nov 2026.
What to do
Upgrade ThinkRank SEO (WordPress plugin) to 2.21.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ThinkRank SEO | Affected
| Fixed in
|
AI-suggested
Upgrade the ThinkRank SEO WordPress plugin to version 2.21.4 or later, where this authorization issue has been fixed. No other mitigation steps are indicated.
Description
The ThinkRank SEO WordPress plugin versions before 2.21.4 contain an authorization flaw where users with access to one settings section can read and modify settings in other, more privileged sections. This includes sensitive areas such as integration API keys and robots.txt content.