dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-0950

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 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 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 Spectra WordPress plugin fails to verify post password protection before rendering excerpts via the render_excerpt() and uagb_get_excerpt() functions. This allows unauthenticated visitors to view excerpts from password-protected posts when those posts are displayed in Post Grid, Post Masonry, Post Carousel, or Post Timeline blocks.

MitigationUpdate to a patched version of the Spectra plugin that implements post_password_required() checks before rendering excerpts, or avoid using password-protected posts with Spectra post blocks until the fix is available.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Spectra plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Spectra' (also known as Ultimate Addons for Gutenberg). Note the installed version number.
    Affected if The installed version has not yet implemented post_password_required() checks in render_excerpt() and uagb_get_excerpt() functions (compare your version to the patched release).
  2. Identify active Spectra post blocks
    Review pages/posts containing Post Grid, Post Masonry, Post Carousel, or Post Timeline blocks. Check the WordPress block editor or view page source for uagb/post-grid, uagb/post-masonry, uagb/post-carousel, or uagb/post-timeline block markup.
    Affected if Any of these four block types are present on the site and pulling from posts that have password protection enabled.
  3. Locate password-protected posts
    In WordPress admin, go to Posts > All Posts and look for posts with a lock icon indicating password protection, or query the wp_posts table for posts where post_password is not empty.
    Affected if There are posts with password protection enabled that are also included in the query/display settings of any Spectra post block.
  4. Test unauthenticated excerpt disclosure
    Open a browser in private/incognito mode, navigate to a page displaying a Spectra post block that includes password-protected posts, and observe whether excerpts from those protected posts are visible without entering a password.
    Affected if Excerpts from password-protected posts are displayed to visitors without requiring password entry - this confirms the vulnerability is present and exploitable.

A site is affected if it runs an unpatched version of Spectra with any Post Grid, Post Masonry, Post Carousel, or Post Timeline blocks displaying password-protected posts to unauthenticated 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.

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

Update to a patched version of the Spectra plugin that implements post_password_required() checks before rendering excerpts, or avoid using password-protected posts with Spectra post blocks until the fix is available.

Recommended fix High confidence

2.19.18 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Spectra Gutenberg Blocks' (or 'Ultimate Addons for Gutenberg') plugin
  4. Click 'Update now' to install the latest version, or manually update to version 2.19.18 or later
  5. Verify the update was successful and the version number reflects 2.19.18 or higher

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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