HomeWordPress vulnerabilitiesPublishPress Blocks
PublishPress Blocks vulnerabilities
PublishPress Blocks has 4 known vulnerabilities in this database. The most recent published record is dated 13 Nov 2026.
- Known vulnerabilities
- 4
- Active installs
- 20,000+
- Latest version
- 3.7.8
- Last updated
- 13 Nov 2026
- Most recent
- 13 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-125819 | Medium 5.3 | Up to 3.7.6 | Fixed in a later version (latest 3.7.8) | 9 d ago |
| Cross-site scripting (XSS) CVE-2026-121721 | Medium 6.5 | Up to 3.7.6 | Fixed in a later version (latest 3.7.8) | 9 d ago |
| Sensitive data exposure CVE-2026-121771 | Medium 5.3 | Up to 3.7.6 | Fixed in a later version (latest 3.7.8) | 9 d ago |
| Cross-site scripting (XSS) CVE-2025-8588 | Medium 6.4 | Up to 3.3.4 | Fixed in a later version (latest 3.7.8) | 25 Oct 2025 |
Read the published descriptions
- CVE-2026-125819, 13 Nov 2026
- Missing Authorization vulnerability in PublishPress Gutenberg Blocks advanced-gutenberg allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Gutenberg Blocks: from n/a through 3.7.6. CVE record
- CVE-2026-121721, 13 Nov 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in PublishPress Gutenberg Blocks advanced-gutenberg allows Stored XSS.This issue affects Gutenberg Blocks: from n/a through 3.7.6. CVE record
- CVE-2026-121771, 13 Nov 2026
- 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. CVE record
- CVE-2025-8588, 25 Oct 2025
- The Gutenberg Blocks - PublishPress Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Marker Title' and 'Marker Description' parameters for the Maps block in versions up to, and including, 3.3.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers with contributor-level access and above to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
What to do if you run PublishPress Blocks
If you run PublishPress Blocks, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new PublishPress Blocks vulnerabilities
Free. We email you when a new vulnerability is published for PublishPress Blocks, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.