CVE-2025-7202
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 · uneditedA Cross-Site Request Forgery (CSRF) in Elgato's Key Lights and related light products allows an attacker to host a malicious webpage that remotely controlles the victim's lights.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in Elgato Key Lights and related light products allows an attacker hosting a malicious webpage to send commands to the victim's lights when the user visits the page while on the same network as the lights. The attack exploits the lack of anti-CSRF tokens or origin validation in the light's HTTP control interface.
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
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Elgato Key Light devices on the networkScan the local network for devices responding to HTTP requests, typically on port 80 or 9123. Look for HTTP server banners containing 'Elgato' or device fingerprints matching Elgato Key Light MAC address prefixes (e.g., starting with 00:1A:7D or similar Elgato OUI). Use tools like nmap, arp-scan, or network scanner tools to enumerate devices.Affected if Elgato Key Light devices are found accessible on the local network.
-
Verify the HTTP control interface is accessibleAttempt to access the device's IP address via HTTP using a web browser or curl command. Elgato Key Lights typically expose an HTTP control panel at the root path. Observe if the page loads and displays light control options.Affected if The device HTTP interface is reachable and displays control options without authentication.
-
Check for anti-CSRF token presence in HTTP requestsAccess the HTTP control interface and examine the HTML source or use browser developer tools to inspect network requests. Look for hidden form fields, CSRF tokens, or any token parameters in the requests. Alternatively, capture a request using a proxy and check if the request includes any token or origin validation parameters.Affected if No anti-CSRF tokens, Origin headers, or Referer validation are present in the HTTP control requests.
-
Verify lack of origin validation in HTTP APISend a crafted HTTP request to the device's API endpoints (commonly /elgato/lights or similar paths) with a mismatched or missing Origin header, using curl or similar tool. Observe if the device accepts and processes the request regardless of origin.Affected if The device accepts and executes commands without validating the request Origin or Referer header.
A user is affected if they have Elgato Key Lights with an accessible HTTP control interface that lacks anti-CSRF token validation and origin checking.
Generated from the published advisory. Verify against your own configuration.
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 dataIsolate IoT devices like Elgato Key Lights on a separate network segment (VLAN) to limit exposure, and avoid browsing untrusted websites while on the same network as smart home devices until a firmware patch is available from Elgato.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7202 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7202 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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