PatchTheCVEflaskblog vulnerabilities and fixes
Recent CVEs affecting flaskblog, with upgrade or downgrade steps. 10 tracked.
flaskblog has 10 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 6. Most recent: 2025-08-19. Highest priority: CVE-2025-28104 (score 51/100).
- CVE-2025-55737 MEDIUM 6.5 UPGRADE flaskBlog is a blog app built with Flask
- CVE-2025-55736 MEDIUM 6.5 UPGRADE flaskBlog is a blog app built with Flask
- CVE-2025-55735 MEDIUM 5.4 UPGRADE flaskBlog is a blog app built with Flask
- CVE-2025-55734 MEDIUM 6.5 UPGRADE flaskBlog is a blog app built with Flask
- CVE-2025-53631 MEDIUM 5.4 UPGRADE flaskBlog is a blog app built with Flask
- CVE-2025-28104 CRITICAL 9.1 DOWNGRADE Incorrect access control in laskBlog v2.6.1 allows attackers to access all usernames via a crafted input.
- CVE-2025-28103 MEDIUM 6.4 DOWNGRADE Incorrect access control in laskBlog v2.6.1 allows attackers to arbitrarily delete user accounts via a crafted
- CVE-2025-28102 MEDIUM 6.1 DOWNGRADE A cross-site scripting (XSS) vulnerability in flaskBlog v2.6.1 allows attackers to execute arbitrary web scrip
- CVE-2025-28101 MEDIUM 6.5 DOWNGRADE An arbitrary file deletion vulnerability in the /post/{postTitle} component of flaskBlog v2.6.1 allows attacke
- CVE-2024-22414 MEDIUM 6.5 UPGRADE flaskBlog is a simple blog app built with Flask
FAQ
How do I fix flaskblog vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is flaskblog being exploited right now?
None of the tracked flaskblog CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which flaskblog CVE should I patch first?
CVE-2025-28104 currently ranks highest (51/100): Incorrect access control in laskBlog v2.6.1 allows attackers to access all usernames via a crafted input..