CVE-2026-2512 Code Embed <= 2.5.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Custom Fields
Authenticated attackers can inject arbitrary scripts via custom fields in the Code Embed WordPress plugin, leading to stored XSS execution on victim pages.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-2512?
CVE-2026-2512 is a medium-severity cross-site scripting vulnerability in dartiss Code Embed, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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 `sec_check_post_fields()` only running on the `save_post` hook, while WordPress allows custom fields to be added via the `wp_ajax_add_meta` AJAX endpoint without triggering `save_post`. The `ce_filter()` 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.
Weakness: CWE-79
Which versions are affected by CVE-2026-2512?
How do I fix CVE-2026-2512?
No fix has been published for CVE-2026-2512 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-2512 being exploited?
There is no known exploitation of CVE-2026-2512 in the wild and no public exploit code.
Sources
Also known as GHSA-j4g5-6g63-3xq4.