Unauthorized comment deletion via unchecked commentID
Published Aug 19, 2025 · Updated Aug 19, 2025
Authorization bypass in Dogukan Urker FlaskBlog 2.8.0 and earlier allows remote attackers to delete arbitrary comments. In routes/post.py, the commentDeleteButton handler passes the attacker-controlled commentID directly to Delete.comment() without checking ownership. Network access to the web application and a valid target comment identifier are sufficient; the bounded consequence is unauthorized comment removal.
Summary
What happened
Authorization bypass in Dogukan Urker FlaskBlog 2.8.0 and earlier allows remote attackers to delete arbitrary comments. In routes/post.py, the commentDeleteButton handler passes the attacker-controlled commentID directly to Delete.comment() without checking ownership. Network access to the web application and a valid target comment identifier are sufficient; the bounded consequence is unauthorized comment removal.
The record
- CVE
- CVE-2025-55737
- Published
- Aug 19, 2025
- Updated
- Aug 19, 2025
- Vendor
- Dogukan Urker
- Product
- FlaskBlog
- Classifications
- CWE-639, T1485
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2025CVE publishedPublication date reported by the CVE source.
- Aug 19, 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=<= 2.8.0
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.
Weakness, pattern, technique
Public exploit references
- GitHub advisory comment-deletion 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