dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2018-25118

CRITICAL · 10.0 CVSS v4.0 Published 2025-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
GeoVision embedded IP devices, confirmed on GV-BX1500 and GV-MFD1501, contain a remote command injection vulnerability via /PictureCatch.cgi that enables an attacker to execute arbitrary commands on the device. The vulnerable models have been declared end-of-life (EOL) by the vendor. VulnCheck has observed this vulnerability being exploited in the wild as of 2025-10-19 08:55:13.141502 UTC.

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

Remote command injection vulnerability in GeoVision GV-BX1500 and GV-MFD-MFD1501 IP devices allows unauthenticated attackers to execute arbitrary commands via the /PictureCatch.cgi web endpoint. The affected devices are end-of-life with no vendor patches available.

MitigationSince vendor patches are unavailable for these EOL devices, immediate network isolation is recommended. Long-term remediation requires replacement with supported hardware.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 device model
    Access the device web interface or check the device label/serial to confirm the model is GeoVision GV-BX1500 or GV-MFD-MFD1501
    Affected if Device model is GV-BX1500 or GV-MFD-MFD1501 (or variants)
  2. Verify web service is enabled
    Attempt to access the device IP address on HTTP port 80 or HTTPS port 443 to confirm the web interface is running
    Affected if Web interface is accessible and responds to HTTP/HTTPS requests
  3. Check if PictureCatch.cgi endpoint exists
    Send a request to http://[device-ip]/PictureCatch.cgi and verify the endpoint responds (even with an error)
    Affected if The /PictureCatch.cgi endpoint is present and responds to requests
  4. Confirm lack of vendor patches
    Check GeoVision support resources or product lifecycle documentation to confirm these EOL models no longer receive firmware updates
    Affected if Device is confirmed as end-of-life with no available vendor patches

User is affected if they operate a GeoVision GV-BX1500 or GV-MFD-MFD1501 device with an accessible web interface and the /PictureCatch.cgi endpoint is present.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since vendor patches are unavailable for these EOL devices, immediate network isolation is recommended. Long-term remediation requires replacement with supported hardware.

Recommended fix High confidence
  1. These GeoVision devices (GV-BX1500, GV-MFD1501) have been declared End-of-Life (EOL) by the vendor.
  2. There is no vendor-provided firmware update, patch, or fixed release available for these models.
  3. If the device cannot be retired and replaced, isolate it on a restricted network segment with firewall rules blocking external access to the /PictureCatch.cgi endpoint and other CGI interfaces.
  4. Monitor for indicators of compromise as this vulnerability is being actively exploited in the wild.
Caveat No upgrade path exists; devices are EOL and should be replaced with supported hardware

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-25118 — 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-2018-25118 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