cve.bz

CVE-2026-121771 WordPress Gutenberg Blocks plugin <= 3.7.6 - Sensitive Data Exposure vulnerability

5.3 mediumFix available

Medium (5.3) in publishpress gutenberg blocks.

On this page
Insertion of Sensitive Information Into Sent Data vulnerability in PublishPress Gutenberg Blocks advanced-gutenberg allows Retrieve Embedded Sensitive Data.This issue affects Gutenberg Blocks: from n/a through 3.7.6.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CWE
CWE-201 Insertion of Sensitive Information Into Sent Data
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
Patchstack (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-121771 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121771?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121771?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-121771 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-121771

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-121771](https://cve.bz/cve/badge/CVE-2026-121771.svg)](https://cve.bz/cve/CVE-2026-121771)

HTML:

<a href="https://cve.bz/cve/CVE-2026-121771"><img src="https://cve.bz/cve/badge/CVE-2026-121771.svg" alt="CVE-2026-121771"></a>

Affected

  • publishpress:gutenberg blocks

Versions

From the CNA's record in the CVE List.

ProductAffected
PublishPress Gutenberg Blocksthrough 3.7.6

Fixed in

ProductFixed in
PublishPress Gutenberg Blocks3.7.7

Fix and patched versions

  • PublishPress Gutenberg Blocks: fixed in 3.7.7

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-217 Exploiting Incorrectly Configured SSL/TLS Likelihood: Low
  • CAPEC-612 WiFi MAC Address Tracking Severity: Low
  • CAPEC-613 WiFi SSID Tracking Severity: Low
  • CAPEC-618 Cellular Broadcast Message Request Severity: Low
  • CAPEC-619 Signal Strength Tracking Severity: Low
  • CAPEC-621 Analysis of Packet Timing and Sizes Severity: Low
  • CAPEC-622 Electromagnetic Side-Channel Attack Severity: Low
  • CAPEC-623 Compromising Emanations Attack Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON