dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-8613

HIGH · 7.2 CVSS v3.0 Published 2025-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an authenticated command injection vulnerability in Vacron Camera devices. The flaw exists in the webs.cgi endpoint where user-supplied input to the ping command is not properly validated before being passed to a system call, allowing an authenticated attacker to execute arbitrary code with root privileges.

MitigationApply vendor firmware updates when available. Until then, restrict network access to camera management interfaces to trusted users only, and disable the ping functionality if possible through device configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Vacron camera device on the network
    Scan network for devices with Vacron-specific HTTP headers, or log into the device admin interface and check the system information or about page for the device model and manufacturer
    Affected if The device is a Vacron Camera product and the web management interface is accessible
  2. Confirm webs.cgi endpoint is exposed
    Access the device web interface and navigate to or attempt to access URLs containing 'webs.cgi', or check if the ping functionality page loads
    Affected if The webs.cgi endpoint responds and the ping feature interface is available without being explicitly disabled
  3. Check if authentication is required for the web interface
    Attempt to access the camera web management pages; observe whether a login prompt appears or if access is granted without credentials
    Affected if The web interface permits access without requiring valid authentication credentials, or uses default/weak credentials that could be easily compromised
  4. Determine if ping functionality is enabled
    Locate the network diagnostics or ping feature within the camera admin interface and verify if it is accessible to authenticated users
    Affected if The ping command feature is available and executable through the web interface to authenticated users
  5. Compare installed firmware to any available updates
    Check the device firmware version shown in system settings or status pages, then compare against any release notes or security advisories from Vacron
    Affected if The installed firmware version predates any available security updates addressing command injection vulnerabilities

A Vacron Camera device with an accessible webs.cgi endpoint where the ping feature is enabled and the web interface is reachable by untrusted users is likely vulnerable to CVE-2025-8613.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available. Until then, restrict network access to camera management interfaces to trusted users only, and disable the ping functionality if possible through device configuration.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8613 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data