dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8844

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Responsive Check plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'rspcheck' shortcode in versions up to, and including, 0.0.3. This is due to insufficient input sanitization and output escaping on the 'url' (and 'button') shortcode attributes in the rspc_check_shortcode() function, which are echoed directly into iframe src attributes without esc_attr() or esc_url(). This makes it possible for authenticated attackers, with contributor-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 Responsive Check WordPress plugin suffers from a stored XSS vulnerability in the rspc_check_shortcode() function. The 'url' and 'button' shortcode attributes are echoed directly into iframe src attributes without sanitization or escaping (missing esc_url() and esc_attr()), allowing authenticated contributors+ to inject arbitrary JavaScript.

MitigationUpdate the plugin to a version beyond 0.0.3 that includes proper input sanitization and output escaping, or apply a code fix adding esc_url() and esc_attr() to the shortcode attribute outputs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Confirm Responsive Check plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Responsive Check' plugin, or check the /wp-content/plugins/ directory for a folder named 'responsive-check' or similar.
    Affected if The plugin is present and active in the WordPress installation.
  2. Check plugin version number
    View the plugin main file (usually responsive-check.php or similar in the plugin folder) and look for the version defined in the plugin header comment (e.g., 'Version: 0.0.3'). Compare this against the vulnerable range.
    Affected if Plugin version is 0.0.3 or lower.
  3. Locate the vulnerable shortcode function
    Open the plugin PHP files and search for the function 'rspc_check_shortcode' or 'add_shortcode' call registering 'rspc_check'. Examine the function to see if 'url' and 'button' attributes are used in iframe src without esc_url() and esc_attr().
    Affected if The function exists and outputs shortcode attributes directly without escaping (no esc_url() or esc_attr() calls around the iframe src).
  4. Identify shortcode usage in content
    Search WordPress database or content for the shortcode [rspc_check] being used in posts, pages, or widgets. Check for custom URL or button values passed, e.g., [rspc_check url='...' button='...'].
    Affected if The shortcode is actively used with user-controlled 'url' or 'button' attributes.
  5. Check for authenticated contributor+ access
    In WordPress admin under Users > All Users, verify if any user accounts exist with Contributor, Author, Editor, or Administrator roles who could create or edit content containing the shortcode.
    Affected if Any user with Contributor-level access or higher exists in the system.

If the Responsive Check plugin is installed with version 0.0.3 or lower AND the vulnerable rspc_check_shortcode function outputs unsanitized 'url' or 'button' attributes into iframe src, the site is affected by this stored XSS vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 0.0.3 that includes proper input sanitization and output escaping, or apply a code fix adding esc_url() and esc_attr() to the shortcode attribute outputs.

Have this fixed 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 help mitigating

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-2026-8844 — 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-2026-8844 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