CVE-2026-2512
The Code Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via custom field meta values in all versions up to, and including, 2.5.1.
Published Mar 18, 2026 · updated Jun 17, 2026
The Code Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via custom field meta values in all versions up to, and including, 2.5.1. This is due to the plugin's sanitization function only running on the hook, while WordPress allows custom fields to be added via the AJAX endpoint without triggering . The function then outputs these unsanitized meta values directly into page content without escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Mar 18, 2026 · NIST NVD
Detected
The Code Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via custom field meta values in all versions up to, and including, 2.5.1. This is due to the plugin's sanitization function only running on the hook, while WordPress allows custom fields to be added via the AJAX endpoint without triggering . The function then outputs these unsanitized meta values directly into page co
Jun 17, 2026 · NIST NVD
Updated
The Code Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via custom field meta values in all versions up to, and including, 2.5.1. This is due to the plugin's sanitization function only running on the hook, while WordPress allows custom fields to be added via the AJAX endpoint without triggering . The function then outputs these unsanitized meta values directly into page co
Sources
- CVE.orgVulnerability recordCVE-2026-2512
Official CVE identifier
cve.org - NIST NVDVulnerability recordCVE-2026-2512
The Code Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via custom field meta values in all versions up to, and including, 2.5.1. This is due to the plugin's sanitization function only running on the hook, while WordP
nvd.nist.gov