Security readout for executives and security teams
Plain-English summary
CVE-2026-2512 affects the WordPress Code Embed plugin through version 2.5.1. A logged-in user with Contributor-level access or higher can store script content in custom fields. That script can run for visitors to the affected page, creating risk of account compromise, content manipulation, or visitor targeting.
Executive priority
Treat as a medium-priority website integrity issue. Prioritize internet-facing WordPress sites with multiple content contributors. The main business concern is stored malicious content affecting visitors or administrators, not direct server takeover based on the provided evidence.
Technical view
The flaw is stored cross-site scripting, CWE-79, CVSS 6.4. Sanitization runs on the save_post hook, but WordPress custom fields can be added through wp_ajax_add_meta without triggering that path. Code Embed’s ce_filter() then outputs unsanitized meta values into page content without escaping.
Likely exposure
Exposure is limited to WordPress sites using Code Embed version 2.5.1 or earlier and allowing Contributor-level or higher accounts. Sites with many authors, weak account governance, or compromised contributor accounts face higher practical risk.
Exploitation context
The attacker must authenticate with Contributor-level privileges or above. Public sources do not indicate active exploitation, and this CVE is not listed as KEV in the provided data. Successful abuse results in stored script execution when users access an injected page.
Researcher notes
Key condition is the sanitization gap between save_post and wp_ajax_add_meta, followed by unescaped output in ce_filter(). Validate defensively by reviewing affected versions, code paths, and stored metadata. Avoid assuming unauthenticated impact; the sources specify Contributor-level access and above.
Mitigation direction
- Update Code Embed to a version newer than 2.5.1 if available from the vendor.
- If no fixed release is available, follow vendor guidance and consider disabling the plugin.
- Restrict Contributor and higher accounts to trusted users only.
- Review and remove unnecessary WordPress author accounts.
- Monitor affected posts for suspicious custom field content.
Validation and detection
- Inventory WordPress sites running the Code Embed plugin.
- Confirm installed plugin versions and flag 2.5.1 or earlier.
- Review Contributor, Author, Editor, and Administrator account legitimacy.
- Inspect post custom fields for unexpected script-like content.
- Check vendor changelog or WordPress Trac changeset for remediation status.
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-2512 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
- 6.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/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:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/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/375ed04b-a3cb-4e60-83c8-18bff583aaf4?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/simple-embed-code/trunk/includes/add-embeds.php#L84CVE reference
- https://plugins.trac.wordpress.org/browser/simple-embed-code/trunk/includes/secure.php#L25CVE reference
- https://plugins.trac.wordpress.org/changeset/3482994/CVE 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.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
