dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-30496

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Optoma CinemaX P2 projector (firmware TVOS-04.24.010.04.01, Android 8.0.0) exposes an HTTP API on TCP port 2345 that allows full unauthenticated remote control of the device. The API supports both reading configuration (74 endpoints) and writing/modifying settings including volume, mute, brightness, power, network protocols enable/disable (including TELNET), display modes, and other projector functions. Any device on the same network can control the projector without authentication.

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

The Optoma CinemaX P2 projector with firmware TVOS-04.24.010.04.01 (Android 8.0.0) exposes an unauthenticated HTTP API on TCP port 2345 that provides full remote control of the device. The API includes 74 configuration reading endpoints and allows modification of critical settings including volume, mute, brightness, power state, network protocol toggles (including enabling TELNET), and display modes. Any attacker with network adjacency can exploit this with no authentication required.

MitigationIsolate the projector on a restricted network segment with firewall rules blocking unauthorized access to TCP port 2345 from untrusted networks; consider network access control (NAC) to limit which devices can communicate with the projector.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 target device is Optoma CinemaX P2
    Check the device's web interface, DHCP fingerprint, or manufacturer label to confirm the model is Optoma CinemaX P2. You can also probe the HTTP service on common ports (80, 443, 8080) and look for Optoma-specific HTTP headers or the CinemaX P2 login page.
    Affected if The device is an Optoma CinemaX P2 projector and matches the firmware version range.
  2. Check if TCP port 2345 is open and listening
    Run a port scan against the target: 'nmap -p 2345 -sV <target_ip>' or 'nc -zv <target_ip> 2345'. Alternatively, use a browser or curl to request http://<target_ip>:2345/.
    Affected if TCP port 2345 is open and accepts HTTP requests, indicating the unauthenticated API is exposed.
  3. Confirm the API accepts unauthenticated requests
    Send an HTTP GET request to a known endpoint on port 2345. For example: 'curl -v http://<target_ip>:2345/<any_path>' or access it via browser. Observe if a response is returned without any login or credentials.
    Affected if The HTTP API responds without requiring authentication, returning configuration data or device status.
  4. Verify firmware version matches affected release
    Access the projector's web interface (port 80/443) or use the API to retrieve firmware version information. Look for version string 'TVOS-04.24.010.04.01' or compare against the affected version range.
    Affected if Firmware version is TVOS-04.24.010.04.01 (Android 8.0.0), confirming the vulnerable release.

A user is affected if they have an Optoma CinemaX P2 projector running firmware TVOS-04.24.010.04.01 with TCP port 2345 exposed to an untrusted network, allowing unauthenticated remote control via the HTTP API.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate the projector on a restricted network segment with firewall rules blocking unauthorized access to TCP port 2345 from untrusted networks; consider network access control (NAC) to limit which devices can communicate with the projector.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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