Unauthenticated token disclosure via unchecked metadata access
Published Jan 27, 2023 · Updated Apr 8, 2026
Missing authorization in ContentStudio for WordPress 1.2.5 and earlier allows remote attackers to read blog metadata without authentication. The cstu_get_metadata function returns arbitrary metadata, including the contentstudio_token, without performing a capability check. No account is required; exposure of the token permits additional plugin interactions, including post creation on versions before 1.2.5.
Summary
What happened
Missing authorization in ContentStudio for WordPress 1.2.5 and earlier allows remote attackers to read blog metadata without authentication. The cstu_get_metadata function returns arbitrary metadata, including the contentstudio_token, without performing a capability check. No account is required; exposure of the token permits additional plugin interactions, including post creation on versions before 1.2.5.
The record
- CVE
- CVE-2023-0556
- Published
- Jan 27, 2023
- Updated
- Apr 8, 2026
- Vendor
- ContentStudio
- Product
- ContentStudio
- Classifications
- CWE-862, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2023CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record 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.2.5
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