CVE-2024-13681: The Uncode theme for WordPress is vulnerable to arbitrary file read due to insufficient input validation in th

Q: How do I fix CVE-2024-13681?

uncode: upgrade to 2.9.1.7. Exact commands for each OS are on this page.

Q: Is CVE-2024-13681 being exploited?

CVE-2024-13681 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-13681 affect?

CVE-2024-13681 affects uncode. Severity is high (CVSS 7.5). The 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 att

Q: How urgent is CVE-2024-13681?

Priority 44/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2024-13681 is a high-severity flaw (CVSS 7.5) affecting uncode. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The 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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-20
Published	2025-02-18
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: undsgn

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-02-18 11:15 UTCPublished CVE record published
2026-06-17 07:02 UTCUpdated Record last modified

undsgn uncode UPGRADE

Affected: < 2.9.1.7

Fixed in: 2.9.1.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy uncode || rpm -q uncode || uncode --version

2. UPGRADE to 2.9.1.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade uncode

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade uncode

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-13681?

uncode: upgrade to 2.9.1.7. Exact commands for each OS are on this page.

Is CVE-2024-13681 being exploited?

CVE-2024-13681 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-13681 affect?

CVE-2024-13681 affects uncode. Severity is high (CVSS 7.5). The 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 att

How urgent is CVE-2024-13681?

Priority 44/100. High severity; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-13691 MEDIUM 6.5 UPGRADE The Uncode theme for WordPress is vulnerable to arbitrary file read due to insufficient input validation in th
CVE-2024-13667 MEDIUM 5.4 UPGRADE The Uncode theme for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘mle-description’ paramete

References

← Back to latest CVEs