dbcve.org
Responsive BlocksWordPress extension · Cyberchimps

CVE-2025-22697

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-04
Fix available
A fix is available. Upgrade to 2.0.0 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 ('Cross-site Scripting') vulnerability in CyberChimps Responsive Blocks responsive-block-editor-addons allows Reflected XSS.This issue affects Responsive Blocks: from n/a through <= 1.9.9.

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

Reflected XSS vulnerability in CyberChimps Responsive Blocks (responsive-block-editor-addons) WordPress plugin allows attackers to inject malicious JavaScript via unsanitized user input that gets reflected back in web pages. The vulnerability affects versions through 1.9.9.

MitigationUpdate to a patched version of the plugin once available; until then, implement input validation and output encoding on all user-supplied parameters, or deploy a WAF with XSS protection rules.

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
Responsive BlocksWordPress extension
Affected:< 2.0.0

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 the plugin installation directory
    Check the WordPress plugins folder (wp-content/plugins/) for a folder named 'responsive-block-editor-addons' or similar naming pattern for CyberChimps Responsive Blocks
    Affected if The plugin folder exists in the WordPress installation
  2. Read the plugin version
    Open the main plugin PHP file (usually plugin-name.php or index.php inside the plugin folder) and look for the 'Version' header in the plugin comment block, or search for a version constant
    Affected if The reported version is less than 2.0.0 (versions 1.x.x through 1.9.9 are affected)
  3. Confirm the plugin is active
    Query the WordPress database 'wp_options' table for option_name='active_plugins' and check if the plugin file path appears in the serialized array, or check via WordPress admin dashboard
    Affected if The plugin appears in the list of active plugins
  4. Identify the vulnerable request pattern
    Review web server access logs for requests to pages using this plugin that contain unsanitized query parameters (common XSS patterns include <script>, javascript:, onerror=, onload= in URL parameters)
    Affected if Requests contain suspicious JavaScript vectors in parameters used by this plugin
  5. Check for existing compromise indicators
    Inspect page source of frontend pages using the plugin blocks for unexpected inline scripts or external script references that were not authored by site administrators
    Affected if Unexpected JavaScript code appears in rendered pages

A user is affected if CyberChimps Responsive Blocks plugin version is below 2.0.0 and is active on their WordPress site, with the vulnerable parameter accepting and reflecting user input without sanitization.

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.0.0 or later
Fixed in 2.0.0
Interim mitigation

Update to a patched version of the plugin once available; until then, implement input validation and output encoding on all user-supplied parameters, or deploy a WAF with XSS protection rules.

Recommended fix Moderate confidence

Upgrade to Responsive Blocks version 2.0.0 or later

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Responsive Blocks' (also known as 'Responsive Block Editor Addons')
  4. 4. If the plugin shows version 1.9.9 or lower, update it to version 2.0.0 or later
  5. 5. After updating, verify the new version number reflects 2.0.0 or higher
  6. 6. Test that the Responsive Blocks editor functionality works correctly after the update

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

Fix this in Responsive Blocks Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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