dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-13607

CRITICAL · 9.4 CVSS v3.1 Published 2025-12-10
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
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
A malicious actor can access camera configuration information, including account credentials, without authenticating when accessing a vulnerable URL.

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

This is an authentication bypass vulnerability in camera firmware/web interface that allows unauthenticated attackers to access sensitive configuration data, including administrative account credentials, through a specific vulnerable URL endpoint. The lack of authentication check on this endpoint exposes plaintext credentials stored in the camera configuration.

MitigationImmediately restrict network access to camera management interfaces via firewall rules or network segmentation. Identify and change all exposed credentials. Contact the camera vendor for firmware updates and apply them promptly once available.

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

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

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 camera model and firmware version
    Access the camera's web interface or use the manufacturer's discovery tool to retrieve the device model number and installed firmware version. Consult the vendor's release notes or security advisory to compare against any published affected versions.
    Affected if The installed firmware version falls within an affected range if the vendor has published specific version details, or the model is known to contain the vulnerability.
  2. Verify network exposure of camera management interface
    Scan the camera's IP address for open HTTP/HTTPS ports (typically 80, 443, or vendor-specific ports) using a tool like nmap: nmap -p 80,443,8080 <camera_ip>. Confirm whether the interface is reachable from untrusted networks.
    Affected if The camera's web interface is directly exposed to the internet or untrusted networks without firewall protection.
  3. Test for unauthenticated endpoint access
    Attempt to access common configuration dump or status endpoints on the camera without providing login credentials. Examples include paths like /config, /settings, /status, or /backup. Use curl or a browser to send an unauthenticated GET request.
    Affected if The camera returns configuration data, credential dumps, or sensitive information without requiring any authentication token or session.
  4. Inspect response for plaintext credentials
    Examine the response from any accessible endpoint for patterns matching usernames and passwords. Look for fields labeled admin, password, user, credentials, or similar. Verify if passwords appear in plaintext rather than being masked or hashed.
    Affected if The response contains plaintext administrative credentials, username/password pairs, or exposed configuration data without requiring authentication.
  5. Check authentication behavior on sensitive endpoints
    Compare the authentication requirements between the login page and specific configuration endpoints. Use browser developer tools or curl to observe HTTP status codes and redirects for both authenticated and unauthenticated requests.
    Affected if The vulnerable endpoint returns 200 OK with content instead of redirecting to a login page, indicating the authentication check is missing.

Your environment is affected if the camera firmware contains the vulnerability and the specific endpoint is accessible without authentication, returning plaintext credentials or sensitive configuration data.

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

Immediately restrict network access to camera management interfaces via firewall rules or network segmentation. Identify and change all exposed credentials. Contact the camera vendor for firmware updates and apply them promptly once available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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