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

CVE-2026-5711

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
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 Post Blocks & Tools plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'sliderStyle' block attribute in the Posts Slider block in all versions up to, and including, 1.3.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with author-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 Post Blocks & Tools WordPress plugin before 1.3.1 suffers from a stored XSS vulnerability in the Posts Slider block's 'sliderStyle' attribute. Authenticated attackers with author-level permissions can inject malicious JavaScript through unsanitized block attributes, which executes when other users access the affected pages.

MitigationUpgrade to version 1.3.1 or later, which includes proper input sanitization and output escaping for the sliderStyle attribute. If immediate upgrade is not possible, restrict author-level access to block editing until the patch is applied.

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. Verify Post Blocks & Tools plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Post Blocks & Tools' or check the plugin directory wp-content/plugins/post-blocks-and-tools/ for the main plugin file
    Affected if The plugin is installed and active in WordPress
  2. Check the installed plugin version
    In Plugins > Installed Plugins, click on the plugin to view details, or open the main plugin PHP file (e.g., post-blocks-and-tools.php) and locate the 'Version' header in the plugin comment block
    Affected if The version number is 1.3.0 or lower (e.g., 1.3.0, 1.2.9, 1.2.0, etc.)
  3. Identify posts or pages using the Posts Slider block
    Search your WordPress database for posts containing the Posts Slider block markup, or use the WordPress block editor to search for pages containing the 'Posts Slider' block; check wp_posts table for block JSON in post_content field
    Affected if Any posts or pages contain the Posts Slider block in use
  4. Inspect the sliderStyle attribute values
    For each post using the Posts Slider block, examine the block's attributes in the post_content (look for 'sliderStyle' or similar attributes in the block JSON); manually inspect or query the database for posts containing 'posts-slider' block type and examine the JSON attributes
    Affected if The sliderStyle attribute contains unsanitized or unescaped content, or contains script tags, event handlers (onclick, onload, etc.), or suspicious JavaScript code
  5. Check for malicious script injection in rendered output
    View a page with the Posts Slider block in a browser, inspect the page source, or query the database directly: SELECT * FROM wp_posts WHERE post_content LIKE '%sliderStyle%'; manually inspect attribute values for script tags or encoded JavaScript
    Affected if Malicious JavaScript code is present in the sliderStyle attribute values and executes when the page loads

If Post Blocks & Tools plugin version 1.3.0 or lower is installed AND the Posts Slider block is in use with unsanitized sliderStyle attribute containing script tags or JavaScript event handlers, the environment 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.3.1 or later, which includes proper input sanitization and output escaping for the sliderStyle attribute. If immediate upgrade is not possible, restrict author-level access to block editing until the patch is applied.

Recommended fix High confidence

1.3.1 or latest available version

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the 'Post Blocks & Tools' plugin
  4. Check if the current version is 1.3.0 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, manually download the fixed version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the version number reflects the patched release

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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