CVE-2024-10814
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Code Embed WordPress plugin contains an SSRF vulnerability in the ce_get_file() function affecting versions up to 2.5. Authenticated attackers with contributor-level permissions can make arbitrary web requests from the server, potentially accessing internal services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Code Embed plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Code Embed' in the listAffected if Code Embed plugin is active on the site
-
Check installed Code Embed versionIn Plugins list, click on the Code Embed plugin to view its version number, or check the plugin header in /wp-content/plugins/code-embed/ folderAffected if Version is 2.5 or lower (including any 2.x.x version below 2.5)
-
Determine if ce_get_file function is accessibleSearch plugin files for ce_get_file() function calls and check if any endpoints or AJAX actions expose it to logged-in usersAffected if ce_get_file function is exposed via admin-ajax.php or other accessible endpoints without proper authorization checks
-
Review user role permissionsCheck WordPress user roles: go to Users > All Users and identify any accounts with Contributor role or higher that should not have posting capabilitiesAffected if There are Contributor-level or higher users who should not have publishing permissions, or if any untrusted users exist at these levels
-
Inspect plugin configuration for URL acceptanceCheck Code Embed settings for any fields accepting URLs (such as for embedding external content) that could be leveraged for SSRFAffected if Plugin settings allow arbitrary URLs to be submitted without validation
You are affected if the Code Embed plugin is installed, the version is 2.5 or lower, and the ce_get_file function is accessible to authenticated users with Contributor-level access or higher.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Code Embed plugin to the latest version once available, or implement proper input validation and access controls on the ce_get_file() function to restrict allowable request targets.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10814 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data