CVE-2026-16983

Gutentor – Gutenberg Blocks – Page Builder for Gutenberg Editor < 4.0.6 - Authenticated (Subscriber+) Password-Protected Post Password Disclosure

2026-08-31 00:00
Ezekiel Victor

Strategic Overview

Status
Patched in 4.0.6
Affected Plugin
Gutentor – Gutenberg Blocks – Page Builder for Gutenberg Editor
Affected Version
< 4.0.6
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-16983
View all Gutentor – Gutenberg Blocks – Page Builder for Gutenberg Editor vulnerabilities

At a glance

CVE-2026-16983 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Gutentor WordPress plugin, affecting versions < 4.0.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.0.6; sites on affected versions should update now. Disclosed August 2026, reported by Ezekiel Victor.

Vulnerability Overview

The Gutentor – Gutenberg Blocks – Page Builder for Gutenberg Editor plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 4.0.6. This is due to missing context and capability check before including post_password in REST API response data, exposing the plaintext password to any authenticated user. This makes it possible for authenticated attackers, with subscriber-level access and above, to retrieve the plaintext passwords of password-protected posts via the plugin's REST endpoint.

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 interaction from a victim user.

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

Reaching this weakness in Gutentor < 4.0.6 takes an account at Subscriber level or above. 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 Gutentor the fix is 4.0.6: builds < 4.0.6 are affected, anything from 4.0.6 onward is not.

Remediation

Update to version 4.0.6, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Gutentor 4.0.6 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-16983https://www.wordfence.com/threat-intel/vulnerabilities/id/abb66687-d0d1-466b-8552-a40bd21a2918https://nvd.nist.gov/vuln/detail/CVE-2026-16983

Related records

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