CVE-2026-0950

Spectra Gutenberg Blocks <= 2.19.17 - Unauthenticated Information Disclosure in Sensitive Data

2026-02-02 16:58
johska

Strategic Overview

Status
Patched in 2.19.18
Affected Plugin
Spectra Legacy – Gutenberg Blocks
Affected Version
<= 2.19.17
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-0950
View all Spectra Legacy – Gutenberg Blocks vulnerabilities

At a glance

CVE-2026-0950 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Spectra Legacy WordPress plugin, affecting versions <= 2.19.17. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.19.18; sites on affected versions should update now. Disclosed February 2026, reported by johska.

Vulnerability Overview

The Spectra Gutenberg Blocks – Website Builder for the Block Editor plugin for WordPress is vulnerable to Information Disclosure in all versions up to, and including, 2.19.17. This is due to the plugin failing to check `post_password_required()` before rendering post excerpts in the `render_excerpt()` function and the `uagb_get_excerpt()` helper function. This makes it possible for unauthenticated attackers to read excerpts of password-protected posts by simply viewing any page that contains a Spectra Post Grid, Post Masonry, Post Carousel, or Post Timeline block.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Spectra Legacy <= 2.19.17 carries this weakness at post_password_required(), and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Spectra Legacy the fix is 2.19.18: builds <= 2.19.17 are affected, anything from 2.19.18 onward is not.

Remediation

Update to version 2.19.18, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Spectra Legacy 2.19.18 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-0950https://www.wordfence.com/threat-intel/vulnerabilities/id/ccaccf03-4162-4365-9f12-0363a78e91d4https://nvd.nist.gov/vuln/detail/CVE-2026-0950

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C