CVE-2025-34130
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 · uneditedAn unauthenticated arbitrary file read exists in LILIN Digital Video Recorder (DVR) devices prior to firmware version 2.0b60_20200207 via the /z/zbin/net_html.cgi endpoint. This vulnerability allows attackers to read sensitive configuration files, such as /zconf/service.xml, which can then be used to facilitate further attacks including command injection. The vulnerability has been exploited in the wild in conjunction with other issues by botnets like FBot and Moobot.
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 confidenceUnauthenticated arbitrary file read vulnerability in LILIN DVR devices via the /z/zbin/net_html.cgi endpoint, allowing attackers to read sensitive configuration files such as /zconf/service.xml without authentication. This can expose credentials and configuration details that facilitate further attacks including command injection.
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:N/VA:N/SC:N/SI:N/SA:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the target is a LILIN DVR deviceSend an HTTP request to the target and examine the response headers, HTML title, or favicon. Look for LILIN branding or product identifiers in the HTTP server header or web interface.Affected if The device is a LILIN DVR and is network-accessible.
-
Verify the /z/zbin/net_html.cgi endpoint is accessibleSend an HTTP GET request to http://target/z/zbin/net_html.cgi without any authentication headers or credentials.Affected if The endpoint returns an HTTP 200 response, indicating the CGI script is present and reachable without authentication.
-
Test for arbitrary file read on /zconf/service.xmlSend a request to /z/zbin/net_html.cgi with a query parameter that attempts to read /zconf/service.xml. Common patterns include adding the file path as a parameter or using path traversal if the endpoint accepts file parameters.Affected if The response contains XML content from /zconf/service.xml, which typically includes service configurations and possibly credentials.
-
Confirm sensitive data exposureExamine the returned content from the previous step. Look for embedded usernames, passwords, configuration values, or other sensitive information within the XML structure.Affected if The retrieved file contains plaintext credentials, API keys, or other sensitive configuration data.
-
Check firmware version if accessibleIf the web interface or a different endpoint reveals firmware version information, note the version number for comparison against the fixed version 2.0b60_20200207.Affected if The installed firmware version is lower than 2.0b60_20200207 or cannot be determined but the arbitrary file read is successful.
The environment is affected if the target is a LILIN DVR device where the /z/zbin/net_html.cgi endpoint is accessible without authentication and successfully returns the contents of /zconf/service.xml or other sensitive files.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade LILIN DVR firmware to version 2.0b60_20200207 or later. If immediate patching is not possible, restrict network access to the device management interface to prevent unauthenticated external access.
Firmware version 2.0b60_20200207
- Identify the LILIN DVR device model in use
- Navigate to the device's administrative web interface or access via the manufacturer's support portal
- Locate the firmware update section or download the firmware version 2.0b60_20200207 from LILIN's official support website
- Follow the manufacturer's instructions to upload and apply firmware version 2.0b60_20200207
- After updating, verify the firmware version has been successfully applied
- Restrict network exposure of the DVR device to only trusted networks or implement firewall rules to limit access to the /z/zbin/net_html.cgi endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-34130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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