# CVE-2025-11852: Apeman ID71 ONVIF Service device_service missing authentication

> Remote attackers can access the ONVIF device service without authentication due to missing authorization checks in the Apeman ID71 camera.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** GHSA-2f45-j73v-44gw

## What is CVE-2025-11852?

CVE-2025-11852 is a medium-severity missing authorization vulnerability in Apeman ID71, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Apeman ID71 218.53.203.117. The impacted element is an unknown function of the file /onvif/device_service of the component ONVIF Service. Performing manipulation results in missing authentication. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2025-11852 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11852 is a medium-severity missing authorization vulnerability in Apeman ID71, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11852 exists.

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

## Sources

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

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