dbcve.org
Unifi VideoApplication · Ui

CVE-2019-5430

HIGH · 8.8 CVSS v3.0 Published 2019-05-06
Fix available
A fix is available. Upgrade to after 3.10.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
In UniFi Video 3.10.0 and prior, due to the lack of CSRF protection, it is possible to abuse the Web API to make changes on the server configuration without the user consent, requiring the attacker to lure an authenticated user to access on attacker controlled page.

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

UniFi Video 3.10.0 and prior contains a CSRF vulnerability in its Web API. Attackers can exploit the lack of CSRF protection to make unauthorized server configuration changes by tricking authenticated users into visiting malicious pages. This requires user interaction (the user must be already authenticated).

MitigationImplement anti-CSRF tokens for state-changing API operations and configure SameSite cookie attributes to prevent cross-site request forgery attacks.

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
Unifi VideoApplication
Affected:<= 3.10.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installed UniFi Video version
    Run 'dpkg -l unifi-video' or 'rpm -qi unifi-video' if installed via package manager; alternatively check the UniFi Video application interface or service info for the version number
    Affected if The installed version is 3.10.0 or lower (including 3.x versions below 3.10.0)
  2. Confirm the UniFi Video service is running
    Run 'systemctl status unifi-video' or 'service unifi-video status' to check if the service is active
    Affected if The service is running and the Web API is accessible on the network
  3. Check if the Web API endpoint is exposed
    Attempt to access the UniFi Video Web API (typically ports 7080, 7443, or 8080) via curl or browser - look for the API response indicating the service is reachable
    Affected if The Web API port is open and responding to HTTP/HTTPS requests, making CSRF attacks possible

If the installed UniFi Video version is 3.10.0 or lower and the Web API is accessible, the environment is vulnerable to the CSRF flaw described in 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
Upgrade available Upgrade to a release after 3.10.0
Interim mitigation

Implement anti-CSRF tokens for state-changing API operations and configure SameSite cookie attributes to prevent cross-site request forgery attacks.

Fix this in Unifi Video Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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