WPGraphQL Smart Cache < 2.0.1 - Unauthenticated Private Content Disclosure
Strategic Overview
- Status
- Patched in 2.0.1
- Affected Plugin
- WPGraphQL Smart Cache
- Affected Version
< 2.0.1- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE pending
At a glance
This record tracks a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WPGraphQL Smart Cache WordPress plugin, affecting versions < 2.0.1. 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.0.1; sites on affected versions should update now. Disclosed December 2025, reported by WPscan.
Vulnerability Overview
The WPGraphQL Smart Cache plugin for WordPress is vulnerable to Information Exposure in all versions up to 2.0.1 (exclusive) via the query endpoint due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to.
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
Reaching this weakness in WPGraphQL Smart Cache < 2.0.1 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 WPGraphQL Smart Cache the fix is 2.0.1: builds < 2.0.1 are affected, anything from 2.0.1 onward is not.
Remediation
Update to version 2.0.1, 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: WPGraphQL Smart Cache 2.0.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C