Security readout for executives and security teams
Plain-English summary
CVE-2026-1266 affects the Postalicious WordPress plugin through version 3.0.1. A logged-in administrator could save malicious script in plugin settings, causing it to run when the affected page is viewed. Business risk is limited by the need for administrator access and specific WordPress configurations, but it can still impact site integrity and user trust.
Executive priority
Treat as a targeted hygiene issue, not an emergency. Prioritize sites using Postalicious in multisite or restricted-HTML configurations, especially where many administrators exist. Remediate during the next plugin maintenance cycle unless suspicious admin activity is observed.
Technical view
The issue is stored cross-site scripting caused by insufficient sanitization and output escaping in Postalicious admin settings. Sources state it affects multisite installations and installations where unfiltered_html is disabled. CVSS is 4.4 with high privileges and high attack complexity. The provided source metadata is inconsistent on affected versions, so confirm against vendor or Wordfence records.
Likely exposure
Exposure is most likely on WordPress sites running Postalicious up to and including 3.0.1, especially multisite deployments or environments with unfiltered_html disabled. Single-site installations with default administrator unfiltered HTML behavior may be less exposed based on the CVE description.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. Exploitation requires an authenticated administrator-level user or higher. This is mainly relevant to compromised admin accounts, malicious insiders, or delegated administrators in multisite environments.
Researcher notes
The CVE description and Wordfence entry identify stored XSS in admin settings. WordPress Trac references point to relevant Postalicious code locations. The affected product metadata in the bundle appears incomplete or inconsistent, so rely on the narrative description and external advisory confirmation for scoping.
Mitigation direction
- Inventory WordPress sites for Postalicious and installed version.
- Review vendor and Wordfence guidance for an official fixed version.
- Disable or remove Postalicious where it is not required.
- Limit administrator access to trusted users only.
- Harden administrator accounts with MFA and credential monitoring.
- Review multisite administrator delegation and unfiltered_html policy.
Validation and detection
- Confirm whether Postalicious is installed on each WordPress site.
- Record plugin version and compare with 3.0.1 or earlier.
- Identify whether the WordPress instance is multisite.
- Check whether unfiltered_html is disabled for relevant administrators.
- Review Postalicious settings for unexpected script-like content.
- Monitor admin activity around plugin settings changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1266 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N1.32.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.4MediumVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/512c9a2f-b023-4e28-8dd8-35795e68a8b3?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/postalicious/trunk/wp-postalicious.php#L316CVE reference
- https://plugins.trac.wordpress.org/browser/postalicious/tags/3.0.1/wp-postalicious.php#L316CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
