# CVE-2025-8613: Vacron Camera ping Command Injection Remote Code Execution Vulnerability

> Remote attackers with authentication can execute arbitrary code as root via command injection in the webs.cgi endpoint of Vacron Cameras.

- **Severity:** High 7.2 (`CVSS:3.0/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:** 2 Sep 2025
- **Updated:** 2 Sep 2025
- **Also known as:** GHSA-479m-726c-mvg5

## What is CVE-2025-8613?

CVE-2025-8613 is a high-severity command injection vulnerability in Vacron Camera, published on 2 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vacron Camera ping Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Vacron Camera devices. Authentication is required to exploit this vulnerability.

The specific flaw exists within the webs.cgi endpoint. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-25892.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-8613 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8613 is a high-severity command injection vulnerability in Vacron Camera, published on 2 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8613 in the wild and no public exploit code.

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

## Sources

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

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