CVE-2025-55737

Public Exploit
flaskBlog arbitrary comment delete

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.

Category

6.9
CVSS
Severity: Medium
CVSS 4.0 •
CVSS 3.1 •
EPSS 0.04%
Third-Party Advisory github.com
Affected: DogukanUrker FlaskBlog
Published at:
Updated at:

References

Link Tags
https://github.com/DogukanUrker/FlaskBlog/security/advisories/GHSA-6hp9-jv2f-88wr third party advisory exploit

Frequently Asked Questions

What is the severity of CVE-2025-55737?
CVE-2025-55737 has been scored as a medium severity vulnerability.
How to fix CVE-2025-55737?
To fix CVE-2025-55737, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2025-55737 being actively exploited in the wild?
It is possible that CVE-2025-55737 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-55737?
CVE-2025-55737 affects DogukanUrker FlaskBlog.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.