# CVE-2024-22414: User profile page vulnerable to Cross Site Scripting (XSS) in flaskBlog

> Attackers can execute arbitrary JavaScript via stored comments in flaskBlog due to unsafe template rendering, requiring manual code modification to fix.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-mrcw-j96f-p6v6

## What is CVE-2024-22414?

CVE-2024-22414 is a medium-severity cross-site scripting vulnerability in DogukanUrker flaskBlog, published on 17 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

flaskBlog is a simple blog app built with Flask. Improper storage and rendering of the `/user/<user>` page allows a user's comments to execute arbitrary javascript code. The html template `user.html` contains the following code snippet to render comments made by a user: `<div class="content" tag="content">{{comment[2]|safe}}</div>`. Use of the "safe" tag causes flask to _not_ escape the rendered content. To remediate this, simply remove the `|safe` tag from the HTML above. No fix is is available and users are advised to manually edit their installation.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-22414?

It affects 1 product.


Products: Dogukanurker Flaskblog.

## How do I fix CVE-2024-22414?

No fix has been published for CVE-2024-22414 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-22414 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22414 exists.

## Other vulnerabilities in DogukanUrker flaskBlog

- [CVE-2025-55736](https://insights.sbomify.com/CVE-2025-55736/): flaskBlog allows arbitrary privilege escalation (critical 9.3)
- [CVE-2025-28104](https://insights.sbomify.com/CVE-2025-28104/): Missing authorization in n/a (critical 9.1)
- [CVE-2025-55734](https://insights.sbomify.com/CVE-2025-55734/): flaskBlo Authorization Bypass (medium 6.9)
- [CVE-2025-55737](https://insights.sbomify.com/CVE-2025-55737/): flaskBlog arbitrary comment delete (medium 6.9)
- [CVE-2025-28101](https://insights.sbomify.com/CVE-2025-28101/): Cross-site request forgery in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22414 and fix it if it is affected.

What it is: CVE-2024-22414 is a medium-severity cross-site scripting vulnerability in DogukanUrker flaskBlog, published on 17 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22414 exists.

Affected product: DogukanUrker flaskBlog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-22414/ (Markdown: https://insights.sbomify.com/CVE-2024-22414/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-22414
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-22414
- OSV: https://osv.dev/vulnerability/CVE-2024-22414

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-22414/
Summaries are generated and may contain mistakes; the official description above is the record.