Security readout for executives and security teams
Plain-English summary
A WordPress plugin that lets visitors submit posts can allow unauthenticated users to store malicious scripts through custom fields. Those scripts run when someone views the affected page. This can expose site visitors or administrators to account/session abuse or content tampering, depending on site configuration.
Executive priority
Treat as a high-priority WordPress exposure for public sites. Patch or disable quickly where the plugin is active, especially on sites with visitor submissions. No active exploitation is confirmed in the provided sources.
Technical view
CVE-2026-0800 is stored cross-site scripting in User Submitted Posts – Enable Users to Submit Posts from the Front End, versions up to and including 20251210. The issue is insufficient input sanitization and output escaping in custom fields. CVSS 3.1 is 7.2 high: network reachable, low complexity, no privileges required, changed scope.
Likely exposure
Exposure is likely limited to WordPress sites running the affected plugin version, especially where front-end submissions and custom fields are enabled. Internet-facing public sites have higher practical risk because unauthenticated users can reach submission workflows.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The vulnerability is still important because it is unauthenticated, stored, and triggered when a user views injected content.
Researcher notes
The public record attributes the flaw to CWE-79. The WordPress Trac changeset is referenced, but the bundle does not clearly name a fixed release. Avoid assuming exploit availability; validate against authoritative plugin and vulnerability records.
Mitigation direction
- Identify all WordPress sites using the User Submitted Posts plugin.
- Update to a vendor-fixed version newer than 20251210 if available.
- If no fix is available, review vendor guidance and consider disabling the plugin.
- Restrict or moderate front-end submissions until remediation is complete.
- Review submitted posts and custom fields for unexpected scripts.
Validation and detection
- Confirm plugin name and installed version on each WordPress site.
- Check whether front-end submissions and custom fields are enabled.
- Verify remediation by confirming the installed version is not affected.
- Inspect recent user-submitted content for suspicious embedded scripts.
- Monitor Wordfence, CVE, and plugin changelog references for updated guidance.
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-0800 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
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/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:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
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.