HomeWordPress vulnerabilitiesCode Embed
Code Embed vulnerabilities
Code Embed has 4 known vulnerabilities in this database. The most recent published record is dated 7 Aug 2026.
- Known vulnerabilities
- 4
- Active installs
- 10,000+
- Latest version
- 2.6.4
- Last updated
- 21 Aug 2026
- Most recent
- 7 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-48093 | Medium 6.5 | Not yet published | Check for an update | 7 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-2512 | Medium 6.4 | Up to 2.5.1 | Fixed in a later version (latest 2.6.4) | 18 Mar 2026 |
| Server-side request forgery (SSRF) CVE-2024-10814 | Medium 6.4 | Up to 2.5 | Fixed in a later version (latest 2.6.4) | 9 Nov 2024 |
| Cross-site scripting (XSS) CVE-2024-8804 | Medium 6.4 | Before 2.5 | Fixed in 2.5 | 4 Oct 2024 |
Read the published descriptions
- CVE-2026-48093, 7 Aug 2026
- 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. CVE record
- CVE-2026-2512, 18 Mar 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 `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. CVE record
- CVE-2024-10814, 9 Nov 2024
- 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. CVE record
- CVE-2024-8804, 4 Oct 2024
- 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. CVE record
What to do if you run Code Embed
If you run Code Embed, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Code Embed vulnerabilities
Free. We email you when a new vulnerability is published for Code Embed, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.