# CVE-2025-48735: SQL injection in IP camera

> Remote attackers can extract sensitive database information from BOS IP cameras via SQL injection in request body processing.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-8w5g-q885-39xw

## What is CVE-2025-48735?

CVE-2025-48735 is a medium-severity SQL injection vulnerability in BOS IP camera, published on 23 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A SQL Injection issue in the request body processing in BOS IPCs with firmware 21.45.8.2.2_220219 before 21.45.8.2.3_230220 allows remote attackers to obtain sensitive information from the database via crafted input in the request body.

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

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


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

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

## Is CVE-2025-48735 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48735 is a medium-severity SQL injection vulnerability in BOS IP camera, published on 23 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48735 in the wild and no public exploit code.

Affected product: BOS IP camera. 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-48735/ (Markdown: https://insights.sbomify.com/CVE-2025-48735/index.md)
```

## Sources

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

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