CVE-2026-1266: Postalicious (WordPress plugin) · Cross-site Scripting
Affects Postalicious (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 4.4 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Jan 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| neopPostalicious | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, restrict administrator access to trusted users only and consider disabling or removing the Postalicious plugin in multi-site environments or where unfiltered_html is disabled. Monitor for updates from the vendor and apply patches promptly once available.
Description
The Postalicious plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 3.0.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
References
- wordfence.com/threat-intel/vulnerabilities/id/512c9a2f-b023-4e28-8dd8-35795e68a8b3?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/postalicious/trunk/wp-postalicious.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/postalicious/tags/3.0.1/wp-postalicious.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/postalicious/trunk/wp-postalicious.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/postalicious/tags/3.0.1/wp-postalicious.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/postalicious/trunk/wp-postalicious.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/postalicious/tags/3.0.1/wp-postalicious.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/postalicious/trunk/wp-postalicious.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/postalicious/tags/3.0.1/wp-postalicious.php (opens in a new tab)