# CVE-2008-10002: cfire24 ajaxlife cross site scripting

> Remote attackers can inject malicious scripts into the ajaxlife web application, potentially compromising user sessions or data.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **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:** 5 Mar 2023
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cqf6-7wvc-xg52

## What is CVE-2008-10002?

CVE-2008-10002 is a low-severity cross-site scripting vulnerability in cfire24 ajaxlife, published on 5 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been found in cfire24 ajaxlife up to 0.3.2 and classified as problematic. This vulnerability affects unknown code. The manipulation leads to cross site scripting. The attack can be initiated remotely. Upgrading to version 0.3.3 is able to address this issue. The patch is identified as 9fb53b67312fe3f4336e01c1e3e1bedb4be0c1c8. It is recommended to upgrade the affected component. VDB-222286 is the identifier assigned to this vulnerability.

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

## Which versions are affected by CVE-2008-10002?

It affects 1 product.


Products: Ajaxlife Project Ajaxlife.

## How do I fix CVE-2008-10002?

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

## Is CVE-2008-10002 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-10002 and fix it if it is affected.

What it is: CVE-2008-10002 is a low-severity cross-site scripting vulnerability in cfire24 ajaxlife, published on 5 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-10002 in the wild and no public exploit code.

Affected product: cfire24 ajaxlife. 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-2008-10002/ (Markdown: https://insights.sbomify.com/CVE-2008-10002/index.md)
```

## Sources

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

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