CVE-2025-53631: flaskBlog is a blog app built with Flask

Q: How do I fix CVE-2025-53631?

flaskblog: upgrade to newer than 2.8.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-53631 being exploited?

CVE-2025-53631 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-53631 affect?

CVE-2025-53631 affects flaskblog. Severity is medium (CVSS 5.4). 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 inc

Q: How urgent is CVE-2025-53631?

Priority 22/100. No elevated risk signals yet.

Routine

MEDIUM 5.4UPGRADE

CVE-2025-53631 is a medium-severity flaw (CVSS 5.4) affecting flaskblog. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.2% (top 88%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-08-14
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: dogukanurker

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-08-14 16:15 UTCPublished CVE record published
2026-06-17 09:38 UTCUpdated Record last modified

dogukanurker flaskblog UPGRADE

Affected: <= 2.8.1

Fixed in: newer than 2.8.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy flaskblog || rpm -q flaskblog || flaskblog --version

2. UPGRADE to newer than 2.8.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade flaskblog

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade flaskblog

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-53631?

flaskblog: upgrade to newer than 2.8.1. Exact commands for each OS are on this page.

Is CVE-2025-53631 being exploited?

CVE-2025-53631 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-53631 affect?

CVE-2025-53631 affects flaskblog. Severity is medium (CVSS 5.4). 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 inc

How urgent is CVE-2025-53631?

Priority 22/100. No elevated risk signals yet.

Software pages

Flask vulnerabilities

Related CVEs

CVE-2025-55737 MEDIUM 6.5 UPGRADE flaskBlog is a blog app built with Flask
CVE-2025-55736 MEDIUM 6.5 UPGRADE flaskBlog is a blog app built with Flask
CVE-2025-55735 MEDIUM 5.4 UPGRADE flaskBlog is a blog app built with Flask
CVE-2025-55734 MEDIUM 6.5 UPGRADE flaskBlog is a blog app built with Flask
CVE-2025-28104 CRITICAL 9.1 DOWNGRADE Incorrect access control in laskBlog v2.6.1 allows attackers to access all usernames via a crafted input.

References

← Back to latest CVEs