dbcve.org
UncodeWordPress extension · Undsgn

CVE-2024-13667

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

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 Stored Cross-Site Scripting via the ‘mle-description’ parameter in all versions up to, and including, 2.9.1.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 suffers from a stored cross-site scripting (XSS) vulnerability in the 'mle-description' parameter. Due to insufficient input sanitization on entry and lack of output escaping on display, authenticated attackers with Subscriber-level permissions can inject malicious JavaScript that executes whenever users view affected pages.

MitigationUpdate the Uncode theme to version 2.9.1.7 or later which contains proper input sanitization and output escaping. If immediate update is not possible, consider disabling the affected mle-description functionality or implementing WAF rules to block malicious payload patterns.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Identify if Uncode theme is installed
    Navigate to wp-content/themes/ in your WordPress installation and check for a folder named 'undcode' or 'Uncode'. Alternatively, check Appearance > Themes in WordPress admin panel for an active or installed theme named 'Undsgn Uncode' or 'Uncode'.
    Affected if The Uncode theme is present in the WordPress installation.
  2. Determine installed Uncode theme version
    Open the file 'style.css' within the Uncode theme folder (wp-content/themes/undcode/) and locate the 'Version:' header in the CSS comment block at the top of the file. Alternatively, check the theme version displayed in WordPress admin under Appearance > Themes > Theme Details.
    Affected if The version number found is less than 2.9.1.7.
  3. Verify if mle-description functionality is accessible
    Check if the theme includes multi-language or 'mle' related options. Look in WordPress admin under Theme Options, or examine the theme's PHP files for 'mle-description' or 'mle' related functions and fields. This feature may appear as a content field in page/post editors or theme customizer settings.
    Affected if The mle-description parameter or related multi-language feature is present and can be edited by users with Subscriber-level permissions.

You are affected if the Uncode theme version is below 2.9.1.7 and the mle-description functionality is enabled or accessible to users with Subscriber-level permissions.

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 version 2.9.1.7 or later which contains proper input sanitization and output escaping. If immediate update is not possible, consider disabling the affected mle-description functionality or implementing WAF rules to block malicious payload patterns.

Recommended fix High confidence

Uncode theme version 2.9.1.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Dashboard > Updates or Appearance > Themes
  3. Locate the Uncode theme and check for available updates
  4. Update the Uncode theme to version 2.9.1.7 or later
  5. Verify the update was successful by checking the theme version in Appearance > Themes

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

Fix this in Uncode Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13667 — 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-13667 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