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 the rendered content. This can lead to a stored XSS inside the content of the post. The code that causes the problem is in template/routes.html.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XDogukanurker Flaskblog
APPDogukanurker≤ 2.8.0
Related vulnerabilities
FlaskBlog: nieuprawniona eskalacja uprawnień do roli administratora
Nieprawidłowa kontrola dostępu w FlaskBlog — ujawnienie nazw użytkowników
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, the code checks if the userRole is "admin" onl...
flaskBlog is a blog app built with Flask. In versions 2.8.1 and prior, improper sanitization of postContent wh...