ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-55735

flaskBlog is a blog app built with Flask.

Published Aug 19, 2025 · catalog updated Aug 19, 2025 · DogukanUrker flaskBlog

Last checked Oct 23, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-55735. EPSS is 0.21%. Act only if a listed version of DogukanUrker flaskBlog is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.21%
Remediation
Advisory link
Affected products
vendor DogukanUrker flaskBlog ≤ 2.8.0

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor DogukanUrker flaskBlog ≤ 2.8.0≤ 2.8.0

How to fix CVE-2025-55735

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-55735. EPSS is 0.21%. Act only if a listed version of DogukanUrker flaskBlog is installed.

Which versions are affected?

Compare what you have installed with DogukanUrker flaskBlog ≤ 2.8.0 ≤ 2.8.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.21%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 19, 2025 · EUVD

    Detected

    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 cau

  2. Aug 19, 2025 · EUVD

    Updated

    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 cau

Sources

  • CVE.orgVulnerability recordCVE-2025-55735

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-55735

    30-day exploitation probability 0.21%

    first.org
  • EUVDVulnerability recordEUVD-2025-25199

    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 en

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 23, 2026
  • CVE.orgOct 22, 2026
  • EUVDOct 22, 2026