CVE-2025-8075
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 · uneditedCybersecurity Nozomi Networks Labs, a specialized security company focused on Industrial Control Systems (ICS) and OT/IoT security, has discovered that validation of incoming XML format request messages is inadequate. This vulnerability could allow an attacker to XSS on the user's browser. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.
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 confidenceThis is a Cross-Site Scripting (XSS) vulnerability caused by inadequate validation of incoming XML format request messages. The lack of proper sanitization of XML input allows attackers to inject malicious scripts that execute in users' browsers when the XML content is rendered or processed by the application.
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< 2.24.00< 2.24.00< 2.24.00< 2.24.00< 2.24.00< 2.23.00< 2.23.00< 2.23.00CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device web interface or use network discovery tools to confirm the exact model number (Xno 8082r, Xnv 8082r, Xnd 8082rf, Xnd 8082rv, Xnb 8002, Pnm 9084qz1, Pnm 9084rqz1, or Pnm 9085rqz1)Affected if The device model matches one of the affected models listed in the CVE
-
Check the installed firmware versionNavigate to the device settings page (typically under System > Information or Device Info) or query the device's web API to retrieve the current firmware versionAffected if The firmware version is below 2.24.00 for Xno 8082r, Xnv 8082r, Xnd 8082rf, Xnd 8082rv, or Xnb 8002, OR below 2.23.00 for Pnm 9084qz1, Pnm 9084rqz1, or Pnm 9085rqz1
-
Confirm XML request processing is enabledInspect the device configuration settings to determine if XML format request message processing is enabled (typically found under Network settings, API settings, or XML configuration options)Affected if XML request processing is enabled and the device accepts XML-based requests
-
Review recent XML-based requestsCheck device logs or network traffic for XML-formatted requests that may contain suspicious content or unexpected script tagsAffected if There are XML requests containing script tags or other potentially malicious content being processed by the device
The device is affected if it is one of the listed Hanwhavision models running firmware below the specified version thresholds and XML request processing is enabled.
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.
dbcve · scoped2.23.002.24.00
Apply the manufacturer's patch firmware as soon as possible. Until patched, disable or restrict processing of untrusted XML requests and monitor for suspicious XML payloads containing script tags.
Firmware 2.24.00 for Xno 8082r/Xnv 8082r/Xnd 8082rf/Xnd 8082rv/Xnb 8002; Firmware 2.23.00 for Pnm 9084qz1/Pnm 9084rqz1/Pnm 9085rqz1
- 1. Identify the affected device model from the list: Xno 8082r, Xnv 8082r, Xnd 8082rf, Xnd 8082rv, Xnb 8002, Pnm 9084qz1, Pnm 9084rqz1, or Pnm 9085rqz1
- 2. Access the device admin interface or console
- 3. Navigate to the firmware update section
- 4. Download the patched firmware from the Hanwha Vision official support website (www.hanwhavision.com)
- 5. Upload and apply the firmware update: for Xno 8082r, Xnv 8082r, Xnd 8082rf, Xnd 8082rv, Xnb 8002 use version 2.24.00 or later; for Pnm 9084qz1, Pnm 9084rqz1, Pnm 9085rqz1 use version 2.23.00 or later
- 6. Verify the firmware version after update is complete
- 7. Confirm the XML input validation fix is applied by reviewing device documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8075 — 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-8075 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