Code Embed · Security record
Is Code Embed safe?
One known vulnerability affects the current version (2.6.4), and it has no fix yet.
Checked 4 days ago against the WPVulnerability database, for version 2.6.4.
How it’s looked after
- Last release
- Aug 21, 2026 (2 months ago)
- Releases in the last year
- 7
- Tested up to
- WordPress 7.1.4
- Active installs
- 10K+
7 known vulnerabilities
- 4 medium
- 3 not rated
1 affects the current version. 1 has no fix yet.
Disclosed each year
- 20141
- 20231
- 20242
- 20262
Every known vulnerability in Code Embed
Newest first, with any that affect the current version at the top.
- medium
Cross-site Scripting
Affects the current version · No fix yet · CVE-2026-48093 · Aug 7, 2026 · CVE
Fixed in 2.5.2 · CVE-2026-2512 · Mar 17, 2026 · Wordfence
Fixed in 2.5.1 · CVE-2024-10814 · Nov 8, 2024 · Wordfence
Fixed in 2.5 · CVE-2024-8804 · Oct 3, 2024 · Wordfence
Fixed in 2.3.7 · CVE-2023-49837 · Dec 5, 2023 · Wordfence
Fixed in 2.0.2 · Aug 1, 2014 · Patchstack
Fixed in 2.0.2 · WPScan
Questions about Code Embed’s security
Is Code Embed safe to use?
Yes: 1 known vulnerability affects version 2.6.4, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Code Embed have known security vulnerabilities?
Yes: 1 known vulnerability affects version 2.6.4, according to WPVulnerability’s database.
Is Code Embed still maintained?
Yes. Its last release was 2 months ago. No support threads were opened in the last two months.
Is Code Embed compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.