# CVE-2025-63667: Missing authorization in n/a

> Attackers can access sensitive API endpoints without authentication in SIMICAM, KEVIEW, and ASECAM camera firmware, leading to unauthorized data access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2025
- **Updated:** 5 Jan 2026
- **Also known as:** GHSA-gwq9-wpwc-v9cf

## What is CVE-2025-63667?

CVE-2025-63667 is a high-severity missing authorization vulnerability in n/a, published on 12 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in SIMICAM v1.16.41-20250725, KEVIEW v1.14.92-20241120, ASECAM v1.14.10-20240725 allows attackers to access sensitive API endpoints without authentication.

Weakness: CWE-284 (Improper Access Control)

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

It affects 3 products.


Products: Asecam Ip Camera Firmware, Keview Ip Camera Firmware, Simicam Ip Camera Firmware.

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

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

## Is CVE-2025-63667 being exploited?

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

Public exploit code:

- Vatilon-based IP camera firmwares issue Session-Id tokens without verifying credentials, allowing attackers to obtain sessions and retrieve plaintext account credentials via API endpoints. (github_poc): https://github.com/Remenis/CVE-2025-63667

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63667 is a high-severity missing authorization vulnerability in n/a, published on 12 Nov 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-63667 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-63667/ (Markdown: https://insights.sbomify.com/CVE-2025-63667/index.md)
```

## Sources

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

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