UncodeWordPress extension · Undsgn
CVE-2024-13681
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 Uncode theme for WordPress is vulnerable to arbitrary file read due to insufficient input validation in the 'uncode_admin_get_oembed' function in all versions up to, and including, 2.9.1.6. This makes it possible for unauthenticated attackers to read arbitrary files on the server.
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 Uncode WordPress theme versions up to 2.9.1.6 contains an arbitrary file read vulnerability in the 'uncode_admin_get_oembed' function due to insufficient input validation, allowing unauthenticated attackers to read any accessible file on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
UncodeWordPress extension
< 2.9.1.7CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Confirm Uncode theme is installedNavigate to WordPress Admin > Appearance > Themes and verify the Uncode theme is installed and/or activeAffected if Uncode theme is present in the WordPress installation
-
Identify installed Uncode versionAccess the theme's style.css file (typically at /wp-content/themes/uncode/style.css) or check the theme version in WordPress Admin > Appearance > Theme Details. Look for the 'Version:' header in the style.css fileAffected if The reported version is below 2.9.1.7 (e.g., 2.9.1.6, 2.9.0, etc.)
-
Check if oembed endpoint is accessibleExamine the theme files for the 'uncode_admin_get_oembed' function (typically in functions.php or includes/oembed.php). Verify if the function handles user input without proper sanitizationAffected if The vulnerable function exists and processes URL parameters without validation
-
Verify unauthenticated access to vulnerable functionTest if the oembed AJAX endpoint is accessible without authentication by reviewing the wp_ajax and wp_ajax_nopriv hooks in the theme that call the uncode_admin_get_oembed functionAffected if The function is hooked to wp_ajax_nopriv, allowing unauthenticated access
A user is affected if the Uncode theme version is below 2.9.1.7 and the vulnerable uncode_admin_get_oembed function is accessible to unauthenticated users.
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.
dbcve · scoped2.9.1.7
Update the Uncode theme to version 2.9.1.7 or later to patch the arbitrary file read vulnerability.
Uncode theme version 2.9.1.7
- Backup your WordPress site before making any changes
- Navigate to Appearance > Themes in the WordPress admin dashboard
- Locate the Uncode theme and update to version 2.9.1.7
- Verify the update was successful by checking the theme version
- Test that the site functionality remains intact after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Uncode
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13681 — 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-13681 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