CVE-2025-55735

Public Exploit
flaskBlog Stored XSS Vulnerability

Description

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.

Category

5.3
CVSS
Severity: Medium
CVSS 4.0 •
CVSS 3.1 •
EPSS 0.06%
Third-Party Advisory github.com
Affected: DogukanUrker FlaskBlog
Published at:
Updated at:

References

Link Tags
https://github.com/DogukanUrker/FlaskBlog/security/advisories/GHSA-gj9v-qhc3-gcfx exploit third party advisory

Frequently Asked Questions

What is the severity of CVE-2025-55735?
CVE-2025-55735 has been scored as a medium severity vulnerability.
How to fix CVE-2025-55735?
To fix CVE-2025-55735, 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-55735 being actively exploited in the wild?
It is possible that CVE-2025-55735 is being exploited or will be exploited in a near future based on public information. 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-55735?
CVE-2025-55735 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.