How severe is CVE-2025-55735?

CVE-2025-55735 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is low, integrity low, and availability none.

Is CVE-2025-55735 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-55735?

CVE-2025-55735 affects Dogukanurker Flaskblog. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-55735?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-55735 have an EU (EUVD) identifier?

Yes. CVE-2025-55735 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-25199.

When was CVE-2025-55735 published?

CVE-2025-55735 was published on 2025-08-19 and last updated on 2026-06-17.

CVE-2025-55735

CVE-2025-55735 is a medium-severity vulnerability in Dogukanurker Flaskblog with a CVSS 3.x base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-79.

Key facts

Severity: Medium (CVSS 3.x base score 5.4)
CVSS v4: 5.3
EPSS exploit prediction: 0% (9th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-25199
Weakness: CWE-79
Affected product: Dogukanurker Flaskblog
Published: 2025-08-19
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-55735?: 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.
How severe is CVE-2025-55735?: CVE-2025-55735 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2025-55735 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-55735?: CVE-2025-55735 affects Dogukanurker Flaskblog. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-55735?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-55735 have an EU (EUVD) identifier?: Yes. CVE-2025-55735 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-25199.
When was CVE-2025-55735 published?: CVE-2025-55735 was published on 2025-08-19 and last updated on 2026-06-17.

References

https://github.com/DogukanUrker/FlaskBlog/security/advisories/GHSA-gj9v-qhc3-gcfx

Affected products (1)

cpe:2.3:a:dogukanurker:flaskblog:*:*:*:*:*:*:*:*

More vulnerabilities in Dogukanurker Flaskblog

CVE-2025-28104 — Critical (CVSS 9.1): Incorrect access control in laskBlog v2.6.1 allows attackers to access all usernames via a crafted input.
CVE-2025-55737 — Medium (CVSS 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…
CVE-2025-55736 — Medium (CVSS 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",…
CVE-2025-55734 — Medium (CVSS 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…
CVE-2025-28101 — Medium (CVSS 6.5): An arbitrary file deletion vulnerability in the /post/{postTitle} component of flaskBlog v2.6.1 allows attackers to…
CVE-2024-22414 — Medium (CVSS 6.5): flaskBlog is a simple blog app built with Flask. Improper storage and rendering of the `/user/<user>` page allows a…

All CVEs affecting Dogukanurker Flaskblog →

Other CWE-79 (Cross-site Scripting (XSS)) vulnerabilities

CVE-2025-49410 — Critical (CVSS 10.0): Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Imran Emu TC…
CVE-2024-47875 — Critical (CVSS 10.0): DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. DOMpurify was vulnerable to…
CVE-2024-6886 — Critical (CVSS 10.0): Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Gitea…
CVE-2023-45144 — Critical (CVSS 10.0): com.xwiki.identity-oauth:identity-oauth-ui is a package to aid in building identity and service providers based on…
CVE-2023-45138 — Critical (CVSS 10.0): Change Request is an pplication allowing users to request changes on a wiki without publishing the changes directly.…
CVE-2022-4361 — Critical (CVSS 10.0): Keycloak, an open-source identity and access management solution, has a cross-site scripting (XSS) vulnerability in the…

Browse all CWE-79 (Cross-site Scripting (XSS)) vulnerabilities →