DogukanUrker FlaskBlog up to 2.8.0 Delete Request routes/post.py authorization

Summaryinfo

A vulnerability identified as problematic has been detected in DogukanUrker FlaskBlog up to 2.8.0. This issue affects some unknown processing of the file routes/post.py of the component Delete Request Handler. This manipulation causes authorization. This vulnerability is registered as CVE-2025-55737. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability has been found in DogukanUrker FlaskBlog up to 2.8.0 and classified as problematic. Affected by this vulnerability is some unknown functionality of the file routes/post.py of the component Delete Request Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2025-55737 since 08/15/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/19/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• DogukanUrker

Name

• FlaskBlog

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8.0

Website

• Product: https://github.com/DogukanUrker/FlaskBlog/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion