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

CVE-2026-5820

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 Zypento Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Table of Contents block in all versions up to, and including, 1.0.6. This is due to the front-end TOC rendering script reading heading text via `innerText` and inserting it into the page using `innerHTML` without proper sanitization. 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 Zypento Blocks WordPress plugin up to version 1.0.6 contains a stored XSS vulnerability in its Table of Contents block. The block's JavaScript reads heading text using innerText but renders it using innerHTML without sanitization, allowing authenticated attackers with Author-level permissions or higher to inject malicious scripts that execute whenever users access the affected pages.

MitigationUpdate the Zypento Blocks plugin to version 1.0.7 or later, which should include proper text sanitization or use of safe DOM methods (textContent) instead of innerHTML when rendering heading text.

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 Zypento Blocks plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Zypento Blocks' in the list
    Affected if The plugin appears in the installed plugins list
  2. Check the installed version
    In Plugins list, click on 'Zypento Blocks' to view the plugin details, or look at the version number displayed in the plugin list
    Affected if The version listed is 1.0.6 or earlier
  3. Identify Table of Contents blocks in use
    Go to Pages or Posts and check if any content was created using the Table of Contents block from Zypento Blocks
    Affected if Table of Contents blocks are present in published content, especially if the content includes headings from untrusted sources
  4. Review user roles with Author access
    In WordPress admin, go to Users > All Users and check which users have the Author role
    Affected if There are any user accounts with Author-level permissions who did not create the affected content themselves

You are affected if Zypento Blocks version 1.0.6 or earlier is installed AND Table of Contents blocks are in use on your site, particularly if untrusted users have Author-level access.

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

Update the Zypento Blocks plugin to version 1.0.7 or later, which should include proper text sanitization or use of safe DOM methods (textContent) instead of innerHTML when rendering heading text.

Recommended fix Moderate confidence

Latest version of Zypento Blocks (version higher than 1.0.6)

  1. 1. Log in to the WordPress admin dashboard with an account that has Administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Zypento Blocks' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the Table of Contents block functions correctly by viewing a page that uses it
  6. 6. Clear any caching plugins or server-side caches to ensure the patched code is served

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

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