# CVE-2025-25876: SQL injection in n/a

> An attacker can exploit SQL injection in Simple ChatBox to obtain sensitive data from the database.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2025
- **Updated:** 24 Feb 2025
- **Also known as:** GHSA-29c4-gq2r-5p78

## What is CVE-2025-25876?

CVE-2025-25876 is a high-severity SQL injection vulnerability in n/a, published on 21 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in ITSourcecode Simple ChatBox up to 1.0. This vulnerability affects unknown code of the file /delete.php. The attack can use SQL injection to obtain sensitive data.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Angeljudesuarez Simple Chatbox.

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

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

## Is CVE-2025-25876 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-25875](https://insights.sbomify.com/CVE-2025-25875/): SQL injection in n/a (medium 6.4)
- [CVE-2025-25877](https://insights.sbomify.com/CVE-2025-25877/): SQL injection in n/a (low 3.8)
- [CVE-2025-25878](https://insights.sbomify.com/CVE-2025-25878/): SQL injection in n/a (low 3.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25876 is a high-severity SQL injection vulnerability in n/a, published on 21 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25876 exists.

Affected product: n/a. 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-25876/ (Markdown: https://insights.sbomify.com/CVE-2025-25876/index.md)
```

## Sources

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

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