Unauthorized comments via missing publication-state check
Published May 16, 2022 · Updated Aug 2, 2024
Incorrect authorization in Publify before 9.2.8 allows remote attackers to post comments on draft or scheduled articles. Article#comments_closed? checks comment settings and the feedback window but omits published?, so the comment controller accepts and saves a comment for unpublished content. No account or user interaction is required, but exploitation requires an unpublished article identifier and alters that article's comment data without exposing its body.
Summary
What happened
Incorrect authorization in Publify before 9.2.8 allows remote attackers to post comments on draft or scheduled articles. Article#comments_closed? checks comment settings and the feedback window but omits published?, so the comment controller accepts and saves a comment for unpublished content. No account or user interaction is required, but exploitation requires an unpublished article identifier and alters that article's comment data without exposing its body.
The record
- CVE
- CVE-2022-0574
- Published
- May 16, 2022
- Updated
- Aug 2, 2024
- Vendor
- Publify
- Product
- Publify
- Classifications
- CWE-284, CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=unspecified <9.2.8
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.
Weakness, pattern, technique
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