Missing AuthenticationWeakness · CWE-306

CVE-2025-12108

CRITICAL · 9.3 CVSS v4.0 Published 2025-11-04
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
The Survision LPR Camera system does not enforce password protection by default. This allows access to the configuration wizard immediately without a login prompt or credentials check.

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

The Survision LPR Camera system ships with password protection disabled by default, allowing unauthenticated attackers to directly access the configuration wizard without any login prompt or credential verification. This results in full administrative access to the device configuration.

MitigationEnable password protection on all Survision LPR cameras, enforce credential requirements before accessing the configuration wizard, and consider network segmentation to limit exposure of unauthenticated management interfaces.

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: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 checks

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

  1. Identify Survision LPR cameras on the network
    Scan your network for devices identified as Survision LPR cameras. Check network device inventories or use network scanning tools to locate devices with Survision vendor identifiers or recognizable LPR camera characteristics.
    Affected if Survision LPR cameras are present in the environment
  2. Test configuration wizard accessibility without authentication
    Attempt to access the device configuration wizard or admin interface by entering the camera IP address in a web browser. Observe whether a login prompt appears before the configuration interface loads.
    Affected if The configuration wizard loads without requiring any credentials or login prompt
  3. Verify password protection status in device configuration
    If you have authenticated access, navigate to the security or authentication settings panel within the device admin interface. Check whether password protection is enabled, enforced, or set as required for configuration access.
    Affected if Password protection is disabled, optional, or not enforced for the configuration wizard
  4. Inspect device default configuration state
    Review the device configuration file or settings export for authentication-related parameters. Look for flags or settings that control whether authentication is mandatory versus optional at first boot or default state.
    Affected if Authentication is configured as optional or disabled by default
  5. Check for unauthenticated configuration change capability
    Attempt to modify device settings such as network parameters, user accounts, or export configurations through the web interface without providing any credentials. Note whether these changes are accepted.
    Affected if Device configuration can be modified without any authentication being required

If Survision LPR cameras are present and the configuration wizard or admin interface is accessible and modifiable without any login or credential verification, the environment is affected by this CVE.

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

Enable password protection on all Survision LPR cameras, enforce credential requirements before accessing the configuration wizard, and consider network segmentation to limit exposure of unauthenticated management interfaces.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12108 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