dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-41016

HIGH · 8.7 CVSS v4.0 Published 2025-11-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
Inadequate access control vulnerability in Davantis DFUSION v6.177.7, which allows unauthorised actors to extract images and videos related to alarm events through access to “/alarms/<ALARM_ID>/<MEDIA>”, where the “MEDIA” parameter can take the value of “snapshot” or “video.mp4”. These media files contain images recorded by security cameras in response to triggered alerts.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in Davantis DFUSION v6.177.7 where the /alarms/<ALARM_ID>/<MEDIA> endpoint lacks proper authorization validation. Attackers can access snapshot and video files from any alarm event by manipulating the ALARM_ID parameter without authentication or authorization checks, exposing sensitive security camera footage.

MitigationImplement robust authentication and authorization checks on the media endpoint to verify user permissions before serving alarm-related media files. Additionally, consider implementing rate limiting and audit logging to detect and deter enumeration attacks.

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 checks

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

  1. Identify if Davantis DFUSION is installed
    Look for the DFUSION application in your environment, typically accessed via web browser on the host running the video management software. Check running services or installed packages for 'dfusion' or 'davantis'.
    Affected if The software is present and running on your system.
  2. Verify the DFUSION version
    Log into the DFUSION admin interface and navigate to the About or System Information section to confirm the exact version number, or check the software's built-in version display.
    Affected if The installed version is 6.177.7.
  3. Test unauthenticated access to the alarms endpoint
    Using a web browser or HTTP client, attempt to access the /alarms/ endpoint directly without providing any authentication credentials. For example: http://<your-dfusion-host>/alarms/1/snapshot.jpg
    Affected if The endpoint returns media files (images or videos) without redirecting to a login page or requiring authentication.
  4. Verify IDOR by enumerating alarm IDs
    Access the /alarms/<ALARM_ID>/<MEDIA> endpoint with different numeric ALARM_ID values (e.g., /alarms/1/, /alarms/100/, /alarms/999/) without authentication. Each request should return different alarm media if the vulnerability exists.
    Affected if Different alarm IDs return different media files without authentication, indicating missing authorization checks.
  5. Confirm media types exposed
    Attempt to access different media file extensions on the alarms endpoint, such as .jpg, .png, .mp4, or .avi without authentication.
    Affected if Snapshot images or video files are served from the /alarms/ endpoint without requiring user authorization.

A user is affected if Davantis DFUSION v6.177.7 is running and the /alarms/<ALARM_ID>/<MEDIA> endpoint serves snapshot or video files without requiring authentication or validating user authorization for the requested alarm ID.

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

Implement robust authentication and authorization checks on the media endpoint to verify user permissions before serving alarm-related media files. Additionally, consider implementing rate limiting and audit logging to detect and deter enumeration attacks.

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-41016 — 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-41016 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