Skip to main content
← Vulnerabilities

On HP Poly EagleEye Cube USB 1.3.1-001267 devices, the administrator authentication flow is broken: session management and access controls…

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

—Not rated
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
5Pcve.now Index 5 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure?/25Exposure: unknown (data gap). No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity?/10Severity: unknown (data gap). No CVSS score or vendor rating
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 60 if added to CISA KEV
  • Would score about 55 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

CVE-2026-39430 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked.

Published
Last modified
Published
Not listed in CISA KEV
5/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

HP Poly EagleEye Cube USB devices running firmware 1.3.1-001267 have a broken administrator login flow, because the device does not enforce session management or access controls on its admin functions. An unauthenticated attacker can skip the login step, using a modified or custom client to call the administrator API directly, change administrator-level settings, and export configuration files that contain the internal administrator and other network credentials.

Read the original description

On HP Poly EagleEye Cube USB 1.3.1-001267 devices, the administrator authentication flow is broken: session management and access controls are not enforced device-side. Thus, an unauthenticated user can change administrator-level settings (without logging in) via a modified client that bypasses the login step or via a custom client to make the underlying administrator API calls. This allows unauthenticated users to perform administrative actions too such as exporting configuration files that include the internal device credentials for the administrator user and other network systems.

Timeline

  1. CVE published
  2. Record last updated
  3. First seen by cve.now

Evidence 3

  1. Repository
  2. Link
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.