Plugins · simple-embed-code · data as of 2026-11-04
Is Code Embed safe? Known vulnerabilities and latest version
- Latest version
- 2.6.4
- Last updated
- 2026-08-21
- Active installs
- 10,000+
- Known issues on record
- 4
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Code Embed provides a very easy and efficient way to embed code (JavaScript, CSS and HTML) in your posts and pages. — by David Artiss
What to do
- Update to the latest version (2.6.4). Anything older than 2.5.2 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get simple-embed-code --field=version shows what you run; wp plugin update simple-embed-code updates it.
Check your version
Known vulnerabilities
4 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.4 CVE-2026-2512 · published 2026-03-18
Stored cross-site scripting (XSS) in Code Embed (2.5.1 and older)
- Affected
- 2.5.1 and older
- Fixed in
- 2.5.2 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-2512Wordfence advisoryCode change (fix)Plugin source
medium 6.4 CVE-2024-10814 · published 2024-11-09
Server-side request forgery (SSRF) in Code Embed (2.5 and older)
- Affected
- 2.5 and older
- Fixed in
- 2.5.1 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Code Embed plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.5 via the ce_get_file() function. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
NVD CVE-2024-10814Wordfence advisoryCode change (fix)Plugin source
medium 5.4 CVE-2024-8804 · published 2024-10-04
Stored cross-site scripting (XSS) in Code Embed (2.4 and older)
- Affected
- 2.4 and older
- Fixed in
- 2.5.1 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Code Embed plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's script embed functionality in all versions up to, and including, 2.4 due to insufficient restrictions on who can utilize the functionality. 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.
medium 6.5 CVE-2023-49837 · published 2024-03-21
Denial of service in Code Embed (2.3.6 and older)
- Affected
- 2.3.6 and older
- Fixed in
- 2.3.7
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Uncontrolled Resource Consumption vulnerability in David Artiss Code Embed.This issue affects Code Embed: from n/a through 2.3.6.
Recent activity
- 2026-08-21 — latest release on wordpress.org (2.6.4).
- 2026-03-18 — Stored cross-site scripting (XSS) disclosed (CVE-2026-2512), fixed in 2.5.2.
- 2024-11-09 — Server-side request forgery (SSRF) disclosed (CVE-2024-10814), fixed in 2.5.1.
- 2024-10-04 — Stored cross-site scripting (XSS) disclosed (CVE-2024-8804), fixed in 2.5.1.
Get an email when Code Embed has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Code Embed (simple-embed-code) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by David Artiss (3 tracked)
Types found in this plugin: Cross-site scripting (XSS) (2) · Server-side request forgery (SSRF) (1) · Denial of service (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/simple-embed-code (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/simple-embed-code"><img src="https://laskyr.com/plugins/simple-embed-code/badge.svg" alt="Code Embed vulnerability status"></a>