Stored XSS via unsafe postContent rendering
Published Aug 14, 2025 · Updated Aug 14, 2025
Stored XSS in Dogukan Urker FlaskBlog 2.8.1 and earlier allows remote authenticated users to execute JavaScript in visitors' browsers. The /createpost handler trusts client-side sanitization, stores postContent without server-side neutralization, and two templates render it through Jinja's safe filter. A logged-in account able to create a post is required; viewing any page containing that post runs the stored script, exposing browser-accessible data or permitting page defacement.
Summary
What happened
Stored XSS in Dogukan Urker FlaskBlog 2.8.1 and earlier allows remote authenticated users to execute JavaScript in visitors' browsers. The /createpost handler trusts client-side sanitization, stores postContent without server-side neutralization, and two templates render it through Jinja's safe filter. A logged-in account able to create a post is required; viewing any page containing that post runs the stored script, exposing browser-accessible data or permitting page defacement.
The record
- CVE
- CVE-2025-53631
- Published
- Aug 14, 2025
- Updated
- Aug 14, 2025
- Vendor
- Dogukan Urker
- Product
- FlaskBlog
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 14, 2025CVE publishedPublication date reported by the CVE source.
- Aug 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 2.8.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-cj43-h8qf-7rw7 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo