The LetterPress WordPress plugin before 2.4.0 does not sanitise and escape some of its settings, which could allow
Source GCVE Database
Not known to be exploited : upgrade to 2.4.0 soon.
Data as of 29 Oct 2026, 07:09 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.4.0
Exploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 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 29 Oct 2026.
What to do
Upgrade LetterPress (WordPress plugin) to 2.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LetterPress | Affected
| Fixed in
|
AI-suggested
Upgrade the LetterPress plugin to version 2.4.0 or later where this issue is fixed. Since the vulnerability affects versions before 2.4.0, applying the official update is the recommended remediation. No other specific mitigations are indicated.
Description
The LetterPress WordPress plugin versions before 2.4.0 do not properly sanitise and escape certain settings. This vulnerability allows high privilege users, such as administrators, to perform Stored Cross-Site Scripting (XSS) attacks even if the unfiltered_html capability is disabled, for example in multisite WordPress setups.