dbcve.org
ResponsiveWordPress extension · Cyberchimps

CVE-2024-35654

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 5.0.3.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 CyberChimps Responsive allows Stored XSS.This issue affects Responsive: from n/a through 5.0.3.

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 exists in the CyberChimps Responsive WordPress theme (versions through 5.0.3) due to improper neutralization of user input during web page generation. The vulnerability allows attackers to inject malicious JavaScript scripts that are stored in the database and executed when other users view affected pages.

MitigationUpdate the Responsive theme to the latest version which should include proper input sanitization and output encoding. Until an official patch is available, implement output escaping using WordPress sanitization functions (such as esc_html(), esc_attr(), or wp_kses()) on all user-generated content before rendering.

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
ResponsiveWordPress extension
Affected:< 5.0.3.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. Identify the installed Responsive theme version
    Access the WordPress admin dashboard, navigate to Appearance > Themes, and locate the Responsive theme. The version number is displayed in the theme details. Alternatively, check the style.css file in the theme directory for the 'Version' header.
    Affected if The installed version is below 5.0.3.1 (versions 5.0.3 and earlier are affected).
  2. Determine if user-generated content is being stored
    Identify which theme templates or functionality handle user input (such as comment forms, contact forms, or custom fields). Since this is a stored XSS, the vulnerability lies in how the theme processes and displays user data that gets saved to the database.
    Affected if The theme processes and displays any form of user-generated content without verification of the installed version.
  3. Inspect theme files for missing output encoding
    Review the theme's PHP files that handle user-generated content output. Look for instances where user data is echoed or printed without using WordPress sanitization functions such as esc_html(), esc_attr(), or wp_kses().
    Affected if Theme files contain output statements for user data that lack proper sanitization functions.
  4. Check for stored malicious scripts in the database
    Examine WordPress database tables (particularly wp_posts, wp_comments, and any custom meta tables) for suspicious script tags, JavaScript event handlers, or iframe elements that may have been injected via the XSS vulnerability.
    Affected if Database entries contain unescaped HTML script tags or JavaScript code in fields that accept user content.

A user is affected if the installed Responsive theme version is below 5.0.3.1 AND the theme handles user-generated content 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 5.0.3.1 or later
Fixed in 5.0.3.1
Interim mitigation

Update the Responsive theme to the latest version which should include proper input sanitization and output encoding. Until an official patch is available, implement output escaping using WordPress sanitization functions (such as esc_html(), esc_attr(), or wp_kses()) on all user-generated content before rendering.

Recommended fix Moderate confidence

5.0.3.1

  1. Upgrade the Responsive theme to version 5.0.3.1 or later to resolve the Stored XSS vulnerability

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

Fix this in Responsive Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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