Incorrect access control in laskBlog v2.6.1 allows attackers to access all usernames via a crafted input.
The attacker sends a specially crafted request to a vulnerable endpoint in the FlaskBlog application, bypassing access control mechanisms. The error classified as CWE-284 (Improper Access Control) indicates that the application does not properly verify the requester's permissions before returning sensitive data. As a result, it is possible to unauthorized read all usernames stored in the system without possessing any account or session.
The attacker obtains a complete list of usernames in the application, which can serve as a starting point for further attacks, such as brute-force password attacks or phishing targeted at specific users. User data confidentiality and integrity are compromised.
Apply patches available from the vendor according to the references. It is recommended to monitor the GitHub repository of the project (https://github.com/DogukanUrker/flaskBlog/issues/130) for information about the release of the patched version. Until the patch is applied, consider restricting access to vulnerable endpoints at the firewall or reverse proxy level.
FlaskBlog v2.6.1 by Dogukanurker
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NDogukanurker Flaskblog
APPDogukanurker2.6.1
Related vulnerabilities
FlaskBlog: nieuprawniona eskalacja uprawnień do roli administratora
flaskBlog is a blog app built with Flask. In 2.8.0 and earlier, the code checks if the userRole is "admin" onl...
flaskBlog is a blog app built with Flask. In 2.8.0 and earlier, when deleting a comment, there's no validation...
flaskBlog is a blog app built with Flask. In 2.8.0 and earlier, when creating a post, there's no validation of...
flaskBlog is a blog app built with Flask. In versions 2.8.1 and prior, improper sanitization of postContent wh...