dbcve.org
Poly Lens DesktopApplication · Hp

CVE-2025-43491

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 2.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 vulnerability in the Poly Lens Desktop application running on the Windows platform might allow modifications to the filesystem, which might lead to SYSTEM level privileges being granted.

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 critical vulnerability in Poly Lens Desktop on Windows allows unauthorized filesystem modifications that can be exploited to achieve SYSTEM-level privileges. This indicates the application likely has excessive permissions or improper access controls that enable an attacker to manipulate files (possibly DLLs, executables, or configuration files) in protected locations, leading to privilege escalation from a lower-privileged context to full system control.

MitigationRestrict filesystem permissions on the Poly Lens Desktop installation directory and related paths to prevent unauthorized modification; apply any available vendor patches; if no patch exists, implement compensating controls such as restricting user permissions and monitoring for suspicious file activity.

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 Lens DesktopApplication
Affected:< 2.3

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Poly Lens Desktop is installed
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\Poly Lens Desktop for the application directory
    Affected if Poly Lens Desktop is present on the system
  2. Determine installed version
    Right-click the executable or check the application's properties, or look for version info in the installation directory
    Affected if The version is lower than 2.3 (e.g., 2.2.x, 2.1.x, etc.)
  3. Inspect filesystem permissions on installation folder
    Right-click the Poly Lens Desktop folder in Program Files, go to Properties > Security, and verify which users have Write or Modify permissions
    Affected if Non-admin users or low-privileged accounts have Write or Modify access to the installation directory
  4. Check for unauthorized file modifications
    Review the installation directory for any recently modified DLLs, executables, or config files, especially unexpected files or backups
    Affected if New or modified files exist in protected directories that were not intentionally placed there

A system is affected if Poly Lens Desktop version 2.3 or higher is not installed and low-privileged users have write access to the application installation directory, allowing potential file manipulation for privilege escalation.

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 2.3 or later
Fixed in 2.3
Interim mitigation

Restrict filesystem permissions on the Poly Lens Desktop installation directory and related paths to prevent unauthorized modification; apply any available vendor patches; if no patch exists, implement compensating controls such as restricting user permissions and monitoring for suspicious file activity.

Recommended fix Moderate confidence

Poly Lens Desktop version 2.3 or later

  1. Navigate to the HP support website (support.hp.com) and locate the Poly Lens Desktop download page
  2. Download the latest version of Poly Lens Desktop (version 2.3 or later)
  3. Run the installer as Administrator
  4. Follow the on-screen installation prompts
  5. Restart the computer after installation completes
  6. Verify the installed version by opening Poly Lens Desktop and checking About/Version information

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

Fix this in Poly Lens Desktop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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