dbcve.org
Dcs 6010l FirmwareOperating system · Dlink

CVE-2025-8155

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A vulnerability has been found in D-Link DCS-6010L 1.15.03 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /vb.htm of the component Management Application. The manipulation of the argument paratest leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

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 · moderate confidence

Stored cross-site scripting (XSS) vulnerability in D-Link DCS-6010L IP camera firmware 1.15.03. The vulnerability exists in the /vb.htm file of the Management Application component where the 'paratest' argument is not properly sanitized, allowing injection of malicious JavaScript code.

MitigationSince the product is end-of-life and no longer supported by D-Link, there is no official firmware patch available. Implement compensating controls such as network isolation, web application firewall rules for the management interface, or replace the device with a supported model.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dcs 6010l FirmwareOperating system
Affected:= 1.15.03

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 the device model
    Access the device's web interface or check the device label to confirm the model is D-Link DCS-6010L
    Affected if The device is not a DCS-6010L model
  2. Check the firmware version
    Log into the camera's web management interface and navigate to the System or Info section to view the firmware version, or use the manufacturer's discovery tool or telnet/ssh if available
    Affected if Firmware version is exactly 1.15.03
  3. Verify Management Application is accessible
    Attempt to access the web-based management interface by entering the camera's IP address in a web browser
    Affected if The management web interface is accessible over HTTP/HTTPS
  4. Confirm the vb.htm endpoint exists
    Navigate to http://[camera_ip]/vb.htm or https://[camera_ip]/vb.htm in a web browser
    Affected if The /vb.htm page loads successfully
  5. Check for the paratest parameter
    View the page source of /vb.htm or attempt to submit the form with the 'paratest' parameter to see if it is reflected in the output without sanitization
    Affected if The 'paratest' parameter is present and user-supplied input is reflected without encoding or sanitization

The environment is affected only if the device is a D-Link DCS-6010L running firmware version 1.15.03 with the Management Application and /vb.htm endpoint accessible, where the 'paratest' parameter accepts unsanitized input.

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 the product is end-of-life and no longer supported by D-Link, there is no official firmware patch available. Implement compensating controls such as network isolation, web application firewall rules for the management interface, or replace the device with a supported model.

Recommended fix Moderate confidence

Migrate to a currently supported D-Link IP camera model (contact D-Link sales or support for current supported models)

  1. 1. Since the D-Link DCS-60100L firmware 1.15.03 is no longer supported by D-Link, there is no official patch available for this XSS vulnerability.
  2. 2. Replace the end-of-life DCS-6010L with a currently supported D-Link network camera model that receives security updates.
  3. 3. If immediate replacement is not possible, restrict network access to the device's management interface using firewall rules or VLAN isolation to limit remote attack surface.
  4. 4. Disable remote management access to the web interface if not required, accessing it only from trusted local networks.
Caveat Replacing the camera may require reconfiguration of associated software, NVR systems, or network settings

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

Fix this in Dcs 6010l Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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