dbcve.org
Poly Clariti ManagerApplication · Hp

CVE-2025-43484

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-23
Fix available
A fix is available. Upgrade to 10.12.2 or later.
See remediation →
68/100
Remediation priority · Elevated
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
A potential reflected cross-site scripting vulnerability has been identified in the Poly Clariti Manager for versions prior to 10.12.1. The website does not validate or sanitize the user input before rendering it in the response. HP has addressed the issue in the latest software update.

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 a reflected cross-site scripting (XSS) vulnerability in Poly Clariti Manager where user-supplied input is not validated or sanitized before being rendered in the HTTP response. An attacker could craft a malicious URL containing JavaScript code that executes in a victim's browser when they click the link. The vulnerability affects versions prior to 10.12.1.

MitigationUpdate Poly Clariti Manager to version 10.12.1 or later where HP has addressed the input validation issue. As a temporary measure, disable the web interface if not required and implement Content Security Policy headers.

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
Poly Clariti ManagerApplication
Affected:< 10.12.2

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify if Poly Clariti Manager is installed
    Look for the Poly Clariti Manager service or application on the system. Check installed programs list, running services, or process list for 'clariti' or 'poly' related processes.
    Affected if Poly Clariti Manager software is present on the system
  2. Determine the installed version
    Access the Poly Clariti Manager web interface and navigate to the About or System Information page, typically found under Settings or Administration. Alternatively, check the software installation directory for version information files or check the Windows Registry under HKLM\SOFTWARE\Poly\ClaritiManager if on Windows.
    Affected if The installed version is lower than 10.12.2
  3. Verify the web interface is enabled
    Confirm the Poly Clariti Manager web service is running by accessing the management URL (commonly https://localhost:8443 or the configured hostname/IP on port 443/8443). Check if the HTTP/HTTPS service is listening.
    Affected if The web interface is accessible and responding to HTTP/HTTPS requests
  4. Confirm reflected input handling
    Test the web application by injecting a benign test string (such as <script>alert(1)</script>) into URL parameters and observing if the input is returned unchanged in the response without HTML encoding.
    Affected if User-supplied input is returned in the response without proper encoding or sanitization

A user is affected if Poly Clariti Manager version 10.12.2 or higher is not installed AND the web interface is accessible AND unvalidated user input is reflected in responses.

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
Upgrade available Upgrade to 10.12.2 or later
Fixed in 10.12.2
Interim mitigation

Update Poly Clariti Manager to version 10.12.1 or later where HP has addressed the input validation issue. As a temporary measure, disable the web interface if not required and implement Content Security Policy headers.

Recommended fix Moderate confidence

Poly Clariti Manager 10.12.2 or later

  1. 1. Back up the current Poly Clariti Manager configuration and data.
  2. 2. Download the latest Poly Clariti Manager software version (10.12.2 or later) from the official HP support portal at support.hp.com.
  3. 3. Review the upgrade documentation and release notes for any prerequisites.
  4. 4. Execute the upgrade following the documented upgrade procedure for Poly Clariti Manager.
  5. 5. After upgrade completion, verify the system is operational and the web interface is accessible.
  6. 6. Confirm the fix is applied by verifying the version number in the system information or about page.

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

Fix this in Poly Clariti Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

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