CVE-2025-53631

flaskBlog XSS Vulnerability in postContent

Description

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 user that made the post. At time of publication, there are no public patches available.

Category

5.3
CVSS
Severity: Medium
CVSS 4.0 •
CVSS 3.1 •
EPSS 0.03%
Vendor Advisory github.com
Affected: DogukanUrker flaskBlog
Published at:
Updated at:

References

Link Tags
https://github.com/DogukanUrker/flaskBlog/security/advisories/GHSA-cj43-h8qf-7rw7 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2025-53631?
CVE-2025-53631 has been scored as a medium severity vulnerability.
How to fix CVE-2025-53631?
To fix CVE-2025-53631, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2025-53631 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-53631 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-53631?
CVE-2025-53631 affects DogukanUrker flaskBlog.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.