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

CVE-2026-6246

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-22
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 Simple Random Posts Shortcode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'container_right_width' attribute of the 'simple_random_posts' shortcode in all versions up to, and including, 0.3 due to insufficient input sanitization and output escaping on user supplied attributes. 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 Simple Random Posts Shortcode WordPress plugin up to version 0.3 contains a stored XSS vulnerability in the 'container_right_width' attribute of the 'simple_random_posts' shortcode. Authenticated attackers with contributor-level access can inject arbitrary JavaScript via this attribute due to missing input sanitization and output escaping, which executes when other users view affected pages.

MitigationUpdate the plugin to a patched version that implements proper input sanitization (e.g., absint() for numeric attributes) and output escaping (e.g., esc_attr()) for all shortcode attributes. Alternatively, remove the plugin if unmaintained.

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. Check if Simple Random Posts Shortcode plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Simple Random Posts Shortcode' or check the plugin files in /wp-content/plugins/ directory for a folder named 'simple-random-posts-shortcode' or similar
    Affected if plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress adminPlugins list, click on the plugin to view details and note the version number, or open the main plugin PHP file and check the Version header in the plugin comment block
    Affected if version is 0.3 or lower (the vulnerable version range)
  3. Identify usage of the vulnerable shortcode
    Search WordPress database via phpmyadmin or WP-CLI: 'wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%simple_random_posts%'"' - look for any posts/pages containing the shortcode
    Affected if the shortcode [simple_random_posts] appears in any published content
  4. Check if container_right_width attribute is in use
    Search post content for 'container_right_width' specifically: 'wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%container_right_width=%'"'
    Affected if any instance of container_right_width= is found in shortcode usage
  5. Verify missing output escaping in plugin code
    Open the main plugin PHP file and search for 'container_right_width' - check if the value is echoed without esc_attr() or similar escaping functions, e.g., look for patterns like 'echo $container_right_width' instead of 'echo esc_attr($container_right_width)'
    Affected if the attribute is output without proper escaping like esc_attr()

User is affected if the plugin is installed at version 0.3 or lower AND the shortcode with container_right_width attribute is used in any content, as the injected JavaScript will execute when viewed by other users

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 patched version that implements proper input sanitization (e.g., absint() for numeric attributes) and output escaping (e.g., esc_attr()) for all shortcode attributes. Alternatively, remove the plugin if unmaintained.

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-6246 — 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-6246 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