The ContentPen WordPress plugin before 1.1.1 discloses its REST API key to unauthenticated users, who can then use it
Source GCVE Database
Not known to be exploited : upgrade to 1.1.1 soon.
Data as of 12 Nov 2026, 07:04 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 1.1.1
Exploitation evidence
Disclosed: evidence found.
CVE published 12 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 11 Nov 2026.
What to do
Upgrade ContentPen (WordPress plugin) to 1.1.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ContentPen | Affected
| Fixed in
|
AI-suggested
A fix is available in ContentPen version 1.1.1. Users should upgrade to version 1.1.1 or later to remediate this vulnerability.
Description
The ContentPen WordPress plugin versions before 1.1.1 expose their REST API key to unauthenticated users. This exposure allows attackers to create posts containing unfiltered JavaScript, resulting in stored cross-site scripting (XSS) that executes in the browsers of any visitors, including administrators.