dbcve.org
InterfaceWordPress extension · Themehorse

CVE-2024-35758

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-21
Fix available
A fix is available. Upgrade to 3.1.1 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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Theme Horse Interface allows Stored XSS.This issue affects Interface: from n/a through 3.1.0.

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 · moderate confidence

A stored Cross-Site Scripting (XSS) vulnerability in Theme Horse Interface theme versions up to 3.1.0 allows authenticated or unauthenticated attackers to inject malicious JavaScript payloads through unsanitized user input. This payload is stored on the server and executes in the browsers of users who view the affected page, potentially leading to session hijacking or credential theft.

MitigationUpdate Theme Horse Interface to version 3.1.1 or later where the patch is applied. Until then, disable the theme or implement WAF rules to filter XSS attack patterns in user inputs.

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
InterfaceWordPress extension
Affected:< 3.1.1

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. Locate Theme Horse Interface theme files
    Access your WordPress installation directory and navigate to wp-content/themes/interface/ to confirm the theme is installed.
    Affected if The theme folder exists in the WordPress themes directory.
  2. Identify installed theme version
    Open the style.css file in the theme directory and look for the 'Version:' declaration in the file header comment block. Alternatively, check functions.php for a version constant.
    Affected if The version number found is lower than 3.1.1 (e.g., 3.1.0, 3.0.x, etc.).
  3. Verify the theme is active
    Log into WordPress admin dashboard and navigate to Appearance > Themes to confirm whether the Interface theme is currently activated on the site.
    Affected if The theme is active and running a version below 3.1.1.
  4. Inspect user input handling
    Review theme files (commonly in template files or widgets) that handle user-submitted content such as comment forms, search inputs, or custom fields. Look for instances where PHP echo or print functions output user data without sanitization functions like esc_html() or esc_attr().
    Affected if Unsanitized user input fields exist and are present in the active theme templates.

Your environment is affected if the Theme Horse Interface theme is installed and active at a version lower than 3.1.1, particularly if the theme accepts and displays user input without proper output encoding.

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 3.1.1 or later
Fixed in 3.1.1
Interim mitigation

Update Theme Horse Interface to version 3.1.1 or later where the patch is applied. Until then, disable the theme or implement WAF rules to filter XSS attack patterns in user inputs.

Recommended fix Moderate confidence

Interface 3.1.1

  1. Update the Interface theme to version 3.1.1 or later via the WordPress theme directory or Theme Horse's official source
  2. After updating, verify the theme version reflects 3.1.1 or higher in the WordPress admin under Appearance > Themes
  3. Clear any site caches if caching plugins are in use to ensure the patched version is fully deployed

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

Fix this in Interface Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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