dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-12351

MEDIUM · 6.8 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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
Honeywell S35 Series Cameras contains an authorization bypass Vulnerability through User controller key. An attacker could potentially exploit this vulnerability, leading to Privilege Escalation to admin privileged functionalities . Honeywell also recommends updating to the most recent version of this product, service or offering (S35 Pinhole/Kit Camera to version 2025.08.28, S35 AI Fisheye & Dual Sensor/Micro Dome/Full Color Eyeball & Bullet Camera to version 2025.08.22, S35 Thermal Camera to version 2025.08.26).

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

Honeywell S35 Series Cameras contain an authorization bypass vulnerability through the User controller key, allowing unauthenticated or low-privileged attackers to escalate privileges to admin-level functionalities.

MitigationUpdate affected cameras to the latest firmware versions: S35 Pinhole/Kit Camera to 2025.08.28, S35 AI Fisheye & Dual Sensor/Micro Dome/Full Color Eyeball & Bullet Camera to 2025.08.22, and S35 Thermal Camera to 2025.08.26.

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 Honeywell S35 Series Camera in environment
    Check network inventory or physically locate devices; look for S35 Pinhole, S35 AI Fisheye, S35 Dual Sensor, S35 Micro Dome, S35 Full Color Eyeball, S35 Bullet, or S35 Thermal Camera models
    Affected if Device model matches any S35 Series variant listed in product documentation
  2. Check firmware version of S35 camera
    Access camera web interface or use manufacturer diagnostic tool to retrieve current firmware version; compare against fixed versions: S35 Pinhole/Kit Camera 2025.08.28, S35 AI Fisheye/Dual Sensor/Micro Dome/Full Color Eyeball/Bullet Camera 2025.08.22, S35 Thermal Camera 2025.08.26
    Affected if Firmware version is older than the fixed release for your specific camera model
  3. Verify User controller key authorization configuration
    Inspect camera authentication settings through web interface or API; examine User controller key endpoint / configuration for proper authorization enforcement on privileged operations
    Affected if User controller key permits unauthenticated access or allows low-privileged users to access admin-level functionalities without proper privilege check

Environment is affected if an S35 Series Camera with firmware older than the fixed version for its model allows unauthorized privilege escalation through the User controller key.

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

Update affected cameras to the latest firmware versions: S35 Pinhole/Kit Camera to 2025.08.28, S35 AI Fisheye & Dual Sensor/Micro Dome/Full Color Eyeball & Bullet Camera to 2025.08.22, and S35 Thermal Camera to 2025.08.26.

Recommended fix High confidence

S35 Pinhole/Kit Camera: version 2025.08.28; S35 AI Fisheye & Dual Sensor/Micro Dome/Full Color Eyeball & Bullet Camera: version 2025.08.22; S35 Thermal Camera: version 2025.08.26

  1. Identify the specific S35 camera model (Pinhole/Kit, AI Fisheye & Dual Sensor/Micro Dome/Full Color Eyeball & Bullet, or Thermal)
  2. Check the current firmware version of the camera through the web interface or management system
  3. Download the appropriate firmware update from Honeywell's official support website
  4. Access the camera's administrative interface and navigate to the firmware update section
  5. Upload and install the firmware update file
  6. Reboot the camera if required and confirm all functionalities are working correctly

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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