CVE-2025-55737— flaskBlog arbitrary comment delete
Quick assessment
Affected
DogukanUrker FlaskBlog
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
FlaskBlog是Doğukan Ürker个人开发者的一个使用 Flask 构建的简单博客应用程序。 FlaskBlog 2.8.0及之前版本存在安全漏洞，该漏洞源于未验证评论所有权可能导致任意删除评论。
Possible ATT&CK Techniques 1 AI
T1059 · Command and Scripting Interpreter
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2025-55737
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
flaskBlog arbitrary comment delete
Source: CVE Program / CVE List V5
Vulnerability Description
flaskBlog is a blog app built with Flask. In 2.8.0 and earlier, when deleting a comment, there's no validation of the ownership of the comment. Every user can delete an arbitrary comment of another user on every post, by simply intercepting the delete request and changing the commentID. The code that causes the problem is in routes/post.py.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
通过用户控制密钥绕过授权机制
Source: CVE Program / CVE List V5
Vulnerability Title
FlaskBlog 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
FlaskBlog是Doğukan Ürker个人开发者的一个使用 Flask 构建的简单博客应用程序。 FlaskBlog 2.8.0及之前版本存在安全漏洞，该漏洞源于未验证评论所有权可能导致任意删除评论。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| DogukanUrker | FlaskBlog | <= 2.8.0 | - |
|
II. Public POCs for CVE-2025-55737
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2025-55737
请登录查看更多情报信息。
Same Patch Batch · DogukanUrker · 2025-08-19 · 4 CVEs total
| CVE-2025-55734 | flaskBlo Authorization Bypass | |
| CVE-2025-55735 | flaskBlog Stored XSS Vulnerability | |
| CVE-2025-55736 | flaskBlog allows arbitrary privilege escalation |
IV. Related Vulnerabilities
Same product: FlaskBlog
Same vendor: DogukanUrker
Same weakness: CWE-639
-
CVE-2026-55867
Graylog token revocation endpoint allows authenticated users -
CVE-2026-19294
Langflow is affected by multiple authentication bypass, path -
CVE-2026-18904
Langflow is affected by multiple authentication bypass, path -
CVE-2026-55067
Vikunja: Authenticated cross-tenant kanban-bucket relocation -
CVE-2026-55066
Vikunja: Cross-tenant IDOR in kanban move-task endpoint via
V. Comments for CVE-2025-55737
No comments yet