# CVE-2025-0228: code-projects Local Storage Todo App index.html cross site scripting

> Remote attackers can inject malicious scripts via the Add argument in the Local Storage Todo App, potentially executing code in victim browsers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2025
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-jh5q-pr4q-x6j4

## What is CVE-2025-0228?

CVE-2025-0228 is a medium-severity cross-site scripting vulnerability in code-projects Local Storage Todo App, published on 5 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability has been found in code-projects Local Storage Todo App 1.0 and classified as problematic. This vulnerability affects unknown code of the file /js-todo-app/index.html. The manipulation of the argument Add leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-0228?

It affects 1 product.


Products: Code-Projects Local Storage Todo App.

## How do I fix CVE-2025-0228?

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

## Is CVE-2025-0228 being exploited?

There is no known exploitation of CVE-2025-0228 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0228 and fix it if it is affected.

What it is: CVE-2025-0228 is a medium-severity cross-site scripting vulnerability in code-projects Local Storage Todo App, published on 5 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0228 in the wild and no public exploit code.

Affected product: code-projects Local Storage Todo App. 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-2025-0228/ (Markdown: https://insights.sbomify.com/CVE-2025-0228/index.md)
```

## Sources

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

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