https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2025-55737.htmlhttps://patchthecve.com/cve/CVE-2025-55737.htmlWed, 17 Jun 2026 09:42:08 +0000MEDIUM 6.5: 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 thahttps://patchthecve.com/cve/CVE-2025-55736.htmlhttps://patchthecve.com/cve/CVE-2025-55736.htmlWed, 17 Jun 2026 09:42:08 +0000MEDIUM 6.5: flaskBlog is a blog app built with Flask. In 2.8.0 and earlier, an arbitrary user can change his role to "admin", giving its relative privileges (e.g. delete users, posts, comments etc.). The problem is in the routes/adminPanelUsers file.https://patchthecve.com/cve/CVE-2025-55735.htmlhttps://patchthecve.com/cve/CVE-2025-55735.htmlWed, 17 Jun 2026 09:42:08 +0000MEDIUM 5.4: flaskBlog is a blog app built with Flask. In 2.8.0 and earlier, when creating a post, there's no validation of the content of the post stored in the variable "postContent". The vulnerability arises when displaying the content of the post using the | safe filter, that tells the engine to not escape thttps://patchthecve.com/cve/CVE-2025-55734.htmlhttps://patchthecve.com/cve/CVE-2025-55734.htmlWed, 17 Jun 2026 09:42:08 +0000MEDIUM 6.5: flaskBlog is a blog app built with Flask. In 2.8.0 and earlier, the code checks if the userRole is "admin" only when visiting the /admin page, but not when visiting its subroutes. Specifically, only the file routes/adminPanel.py checks the user role when a user is trying to access the admin page, buhttps://patchthecve.com/cve/CVE-2025-53631.htmlhttps://patchthecve.com/cve/CVE-2025-53631.htmlWed, 17 Jun 2026 09:38:36 +0000MEDIUM 5.4: flaskBlog is a blog app built with Flask. In versions 2.8.1 and prior, improper sanitization of postContent when submitting POST requests to /createpost leads to arbitrary JavaScript execution (XSS) on all pages the post is reflected on including /, /post/[ID], /admin/posts, and /user/[ID] of the ushttps://patchthecve.com/cve/CVE-2025-28104.htmlhttps://patchthecve.com/cve/CVE-2025-28104.htmlWed, 17 Jun 2026 09:04:34 +0000CRITICAL 9.1: Incorrect access control in laskBlog v2.6.1 allows attackers to access all usernames via a crafted input.https://patchthecve.com/cve/CVE-2025-28103.htmlhttps://patchthecve.com/cve/CVE-2025-28103.htmlWed, 17 Jun 2026 09:04:34 +0000MEDIUM 6.4: Incorrect access control in laskBlog v2.6.1 allows attackers to arbitrarily delete user accounts via a crafted request.https://patchthecve.com/cve/CVE-2025-28102.htmlhttps://patchthecve.com/cve/CVE-2025-28102.htmlWed, 17 Jun 2026 09:04:34 +0000MEDIUM 6.1: A cross-site scripting (XSS) vulnerability in flaskBlog v2.6.1 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the postContent parameter at /createpost.https://patchthecve.com/cve/CVE-2025-28101.htmlhttps://patchthecve.com/cve/CVE-2025-28101.htmlWed, 17 Jun 2026 09:04:34 +0000MEDIUM 6.5: An arbitrary file deletion vulnerability in the /post/{postTitle} component of flaskBlog v2.6.1 allows attackers to delete article titles created by other users via supplying a crafted POST request.