dbcve.org
InjectionWeakness · CWE-74

CVE-2026-7703

HIGH · 7.3 CVSS v3.1 Published 2026-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 flaw has been found in AV Stumpfl Pixera Two Media Server up to 25.2 R2. Impacted is an unknown function of the component Websocket API. This manipulation causes code injection. The attack can be initiated remotely. The exploit has been published and may be used. Upgrading to version 25.2 R3 is recommended to address this issue. Upgrading the affected component is advised.

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 code injection vulnerability exists in the Websocket API of AV Stumpfl Pixera Two Media Server versions up to 25.2 R2. Remote attackers can exploit this to inject malicious code through the websocket interface. The vendor has released version 25.2 R3 which contains the fix for this high-severity issue.

MitigationUpgrade all affected Pixera Two Media Server installations to version 25.2 R3 or later to remediate this vulnerability. Given the published exploit and remote attack vector, prioritization is advised.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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. Confirm Pixera Two Media Server is installed
    Locate the Pixera installation directory or check for the Pixera Two application on the system. Common locations include C:\Program Files\AV Stumpfl\Pixera or /Applications/Pixera on macOS.
    Affected if The software is present on the system
  2. Identify the installed Pixera version
    Open Pixera and navigate to Help > About, or check the application executable properties for version information. The version is typically displayed as a release number like X.X R#.
    Affected if The installed version is 25.2 R2 or earlier (any version prior to 25.2 R3)
  3. Verify websocket API accessibility
    Check if the Pixera websocket API service is running and accessible. This is typically enabled by default for remote control functionality. Consult Pixera documentation for the specific port (commonly 8080 or 8443 for websocket connections).
    Affected if The websocket API endpoint is exposed and accepting connections
  4. Assess exposure to network
    Determine if the Pixera server has a reachable network interface from untrusted networks. Check firewall rules and network configuration to see if the websocket port is open to external IPs.
    Affected if The websocket API is accessible from untrusted or public network segments

A user is affected if Pixera Two Media Server version 25.2 R2 or earlier is installed and the websocket API is accessible (whether locally or over the network).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade all affected Pixera Two Media Server installations to version 25.2 R3 or later to remediate this vulnerability. Given the published exploit and remote attack vector, prioritization is advised.

Recommended fix Moderate confidence

25.2 R3

  1. Back up the current Pixera configuration and any custom settings before starting the upgrade
  2. Download the Pixera version 25.2 R3 update from the official AV Stumpfl website or your licensed distribution channel
  3. Apply the upgrade to the Pixera Two Media Server following the standard installation procedure
  4. After upgrading, verify that the Websocket API is functioning correctly and the version shows 25.2 R3
  5. Test that normal media server operations work as expected
Caveat Minor version update (R2 to R3) with no reported breaking changes; standard upgrade procedure applies

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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