Protected-story disclosure via read-only duplication check
Published May 8, 2023 · Updated Jan 28, 2025
Incorrect authorization in Google Web Stories for WordPress before 1.32 allows remote authenticated users to read protected story content. The REST create_item path accepted an original_id for duplication after checking only read permission, while the response returned story_data without enforcing the post password. An authenticated Author account and a password-protected story are required; successful exploitation discloses that story's protected content.
Summary
What happened
Incorrect authorization in Google Web Stories for WordPress before 1.32 allows remote authenticated users to read protected story content. The REST create_item path accepted an original_id for duplication after checking only read permission, while the response returned story_data without enforcing the post password. An authenticated Author account and a password-protected story are required; successful exploitation discloses that story's protected content.
The record
- CVE
- CVE-2023-1979
- Published
- May 8, 2023
- Updated
- Jan 28, 2025
- Vendor
- Product
- Web Stories for WordPress
- Classifications
- CWE-863, CAPEC-115
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2023CVE publishedPublication date reported by the CVE source.
- Jan 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.32
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo