Comment insertion via tokenless cross-site form submission
Published Jul 19, 2024 · Updated Jul 9, 2026
Cross-site request forgery in ProcessWire 3.0.229 allows remote attackers to submit comments through a victim opening crafted HTML. The comments form accepts a cross-site POST containing comment and page fields without a request token or referrer requirement. The Supplier disputes the vulnerability because anonymous comments are intentional, the Comments field must be enabled, and submissions are held for moderator review by default.
Summary
What happened
Cross-site request forgery in ProcessWire 3.0.229 allows remote attackers to submit comments through a victim opening crafted HTML. The comments form accepts a cross-site POST containing comment and page fields without a request token or referrer requirement. The Supplier disputes the vulnerability because anonymous comments are intentional, the Comments field must be enabled, and submissions are held for moderator review by default.
The record
- CVE
- CVE-2024-41597
- Published
- Jul 19, 2024
- Updated
- Jul 9, 2026
- Vendor
- ProcessWire
- Product
- ProcessWire
- Classifications
- CWE-352, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2024CVE publishedPublication date reported by the CVE source.
- Jul 9, 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=3.0.229
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- ProcessWire comments CSRF proof of conceptproof of concept · demonstrated
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