CVE-2024-13691

Uncode <= 2.9.1.6 - Authenticated (Subscriber+) Arbitrary File Read in uncode_recordMedia

2025-02-17 00:00
mikemyers

Strategic Overview

Status
Patched in 2.9.1.7
Affected Theme
Uncode
Affected Version
<= 2.9.1.6
CVSS
6.5Medium
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE-2024-13691
View all Uncode vulnerabilities

At a glance

CVE-2024-13691 is a medium-severity Improper Input Validation vulnerability in the Uncode WordPress theme, affecting versions <= 2.9.1.6. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.9.1.7; sites on affected versions should update now. Disclosed February 2025, reported by mikemyers.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-20: Improper Input Validation

Uncode <= 2.9.1.6 carries this weakness at uncode_recordMedia, and reaching it takes an account at Subscriber level or above. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For Uncode the fix is 2.9.1.7: builds <= 2.9.1.6 are affected, anything from 2.9.1.7 onward is not.

Remediation

Update to version 2.9.1.7, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Uncode 2.9.1.7 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C