dbcve.org
UncodeWordPress extension · Undsgn

CVE-2024-13691

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to 2.9.1.7 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Uncode theme for WordPress is vulnerable to arbitrary file read due to insufficient input validation in the 'uncode_recordMedia' function in all versions up to, and including, 2.9.1.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 confidence

The Uncode WordPress theme contains an arbitrary file read vulnerability in the 'uncode_recordMedia' function. Due to insufficient input validation, any authenticated user with Subscriber-level access (the lowest privilege tier) can supply malicious file path parameters to read arbitrary files from the server filesystem.

MitigationUpdate the Uncode theme to a version beyond 2.9.1.6 once a patch is released. In the interim, restrict or disable the affected 'uncode_recordMedia' function and audit user role permissions.

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
Affected:< 2.9.1.7

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Uncode theme is installed
    Navigate to Appearance > Themes in WordPress admin, or inspect /wp-content/themes/ directory for the uncode folder
    Affected if The Uncode theme folder exists in the WordPress themes directory
  2. Identify installed Uncode theme version
    Open the theme's style.css file (typically at /wp-content/themes/uncode/style.css) and locate the 'Version:' header in the file comments
    Affected if The version number is less than 2.9.1.7 (for example, 2.9.1.6, 2.9.0.x, etc.)
  3. Locate the vulnerable uncode_recordMedia function
    Search the theme files for 'function uncode_recordMedia' in /wp-content/themes/uncode/ directory using grep or a file search
    Affected if The function exists and is defined in the theme code
  4. Verify if the function is accessible toSubscriber-level users
    Check WordPress user roles under Users > Roles in admin, or inspect role capability definitions in theme files. A Subscriber role typically has only 'read' capability
    Affected if Subscriber role exists and the vulnerable function is hooked to an accessible action/filter without capability checks
  5. Confirm the function is exposed via AJAX or direct access
    Inspect the theme for add_action calls hooking 'wp_ajax_' or 'wp_ajax_nopriv_' actions that call uncode_recordMedia, or check for direct function invocation via admin-ajax.php
    Affected if The uncode_recordMedia function is hooked to an AJAX endpoint accessible to authenticated users including Subscribers

You are affected if the Uncode theme version is below 2.9.1.7, the uncode_recordMedia function exists, and Subscriber-level users can access it without proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.9.1.7 or later
Fixed in 2.9.1.7
Interim mitigation

Update the Uncode theme to a version beyond 2.9.1.6 once a patch is released. In the interim, restrict or disable the affected 'uncode_recordMedia' function and audit user role permissions.

Recommended fix High confidence

Uncode theme version 2.9.1.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. Locate the Uncode theme
  4. If automatic updates are enabled, the theme should update to version 2.9.1.7 automatically
  5. If manual update is needed, download the Uncode theme version 2.9.1.7 from the vendor (support.undsgn.com)
  6. Upload and install the updated theme version
  7. Verify the installed version is 2.9.1.7 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Uncode Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13691 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13691 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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