dbcve.org
Poly Clariti ManagerApplication · Hp

CVE-2025-43022

HIGH · 7.2 CVSS v3.1 Published 2025-07-22
Fix available
A fix is available. Upgrade to 10.12.2 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
A potential SQL injection vulnerability has been identified in the Poly Clariti Manager for versions prior to 10.12.1. The vulnerability could allow a privileged user to execute SQL commands. 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 · moderate confidence

A potential SQL injection vulnerability in Poly Clariti Manager versions prior to 10.12.1 allows a privileged user to execute arbitrary SQL commands due to improper input sanitization in the application.

MitigationUpgrade Poly Clariti Manager to version 10.12.1 or later to apply HP's security patch that addresses the SQL injection vulnerability.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 Poly Clariti Manager installation
    Locate the Poly Clariti Manager application on the system or check the web application serving the management interface, typically accessed via browser on the configured management port
    Affected if Poly Clariti Manager is installed and accessible on the network
  2. Determine installed software version
    Check the application's About page, help menu, or system information within the Poly Clariti Manager web interface, or use system package management commands if accessing the server directly
    Affected if The installed version is earlier than 10.12.2 (any version prior to 10.12.2 is affected)
  3. Verify privileged user access exists
    Review user accounts configured in Poly Clariti Manager to confirm the presence of accounts with administrative or elevated privileges
    Affected if Privileged user accounts are configured and able to authenticate to the manager
  4. Confirm application is reachable over network
    Test network connectivity to the Poly Clariti Manager web interface using the configured hostname or IP address and port
    Affected if The management interface is exposed and reachable

You are affected if Poly Clariti Manager is installed at version 10.12.1 or earlier (below 10.12.2) and privileged users can access the application interface, as the SQL injection requires a privileged authenticated session to exploit.

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

Upgrade Poly Clariti Manager to version 10.12.1 or later to apply HP's security patch that addresses the SQL injection vulnerability.

Recommended fix Moderate confidence

Poly Clariti Manager 10.12.2 or later

  1. Backup current Poly Clariti Manager configuration and data before proceeding with any upgrade
  2. Navigate to HP support website (support.hp.com) and locate the Poly Clariti Manager downloads section
  3. Download Poly Clariti Manager version 10.12.2 or the latest available stable release
  4. Review release notes for any specific upgrade prerequisites or migration requirements
  5. Execute the upgrade installer following standard Poly software upgrade procedures
  6. Verify the upgrade completed successfully by checking the software version in the management interface
  7. Confirm the SQL injection vulnerability is no longer present by validating the fix

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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