CVE-2024-41910
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 vulnerability was discovered in the firmware builds up to 10.10.2.2 in Poly Clariti Manager devices. The firmware contained multiple XSS vulnerabilities in the version of JavaScript used.
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 confidenceMultiple Cross-Site Scripting (XSS) vulnerabilities exist in the JavaScript implementation within Poly Clariti Manager firmware up to version 10.10.2.2. The vulnerability allows attackers to inject malicious scripts through the web management interface due to improper input sanitization, potentially compromising authenticated sessions or executing arbitrary code in user browsers.
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< 10.12.0.2_100CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Poly Clariti Manager is presentIdentify the system as Poly Clariti Manager by checking device/model information, software inventory, or system diagnosticsAffected if The system is not Poly Clariti Manager
-
Determine installed firmware versionAccess the management interface or device diagnostics and locate the firmware version information, typically found in About, System Info, or Settings sectionsAffected if The installed version is below 10.12.0.2_100 (versions 10.10.2.2 and below are affected)
-
Verify web management interface is enabledCheck the device or software configuration to confirm the web-based management interface is currently activeAffected if The web management interface is disabled and not in use
-
Determine authentication requirements for the interfaceReview access control settings to confirm whether the web management interface requires authentication for accessAffected if The interface is accessible without authentication
User is affected if running Poly Clariti Manager with firmware version below 10.12.0.2_100 and the web management interface is enabled and accessible.
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 · scoped10.12.0.2_100
Update Poly Clariti Manager firmware to a version beyond 10.10.2.2. Additionally, restrict network access to the management interface to trusted networks only until the update can be applied.
Poly Clariti Manager firmware 10.12.0.2_100 or later
- Check current Poly Clariti Manager firmware version via the web interface or CLI
- Download firmware version 10.12.0.2_100 or later from HP/Poly support portal (support.hp.com)
- Backup current configuration following Poly documentation
- Upload the new firmware via the device management interface
- Follow standard Poly firmware upgrade procedures including any required reboots
- Verify the device is running the fixed firmware version
- Confirm XSS vulnerabilities are resolved by testing or reviewing release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41910 — 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-2024-41910 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