Comment submission via missing CSRF token
Published Dec 10, 2022 · Updated Apr 15, 2025
Cross-site request forgery in morontt Zend-blog-2 allows remote attackers to submit comments through a victim's browser. The ajaxaddcommentAction endpoint accepted comment POST data and called saveComment without validating a request-bound CSRF token. A victim must interact with attacker-controlled content while able to reach the blog; successful requests create comments with the victim browser's authority.
Summary
What happened
Cross-site request forgery in morontt Zend-blog-2 allows remote attackers to submit comments through a victim's browser. The ajaxaddcommentAction endpoint accepted comment POST data and called saveComment without validating a request-bound CSRF token. A victim must interact with attacker-controlled content while able to reach the blog; successful requests create comments with the victim browser's authority.
The record
- CVE
- CVE-2022-4397
- Published
- Dec 10, 2022
- Updated
- Apr 15, 2025
- Vendor
- morontt
- Product
- Zend-blog-2
- Classifications
- CWE-863, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 10, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 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=n/a
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