WPGraphQL Smart Cache < 2.3.2 - Unauthenticated Persisted Query Registration and Alias Squatting
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-284.
Summary
The WPGraphQL Smart Cache WordPress plugin before 2.3.2 does not require authorisation or validate a caller-supplied query identifier before storing a persisted query from a request, allowing unauthenticated users to publish arbitrary query documents and claim query aliases before a site's own frontend registers them.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | WPGraphQL Smart Cache | before 2.3.2 | 2.3.2 | Patch available | CNA |
- WPGraphQL Smart Cache VendorUnknown Affected before 2.3.2 Fixed in 2.3.2 Patch available CNA
Remediation
- Fix · CNA WPGraphQL Smart Cache (Unknown) Fixed in 2.3.2
Timeline
- 2026-10-02 Threatist record created from CVE-2026-92099
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences