dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-22563

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-13
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
A series of Improper Input Validation vulnerabilities could allow a Command Injection by a malicious actor with access to the UniFi Play network. Affected Products: UniFi Play PowerAmp (Version 1.0.35 and earlier)
 UniFi Play Audio Port  (Version 1.0.24 and earlier)
 Mitigation: Update UniFi Play PowerAmp to Version 1.0.38 or later
 Update UniFi Play Audio Port  to Version 1.1.9 or later

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

Improper input validation in UniFi Play PowerAmp (versions 1.0.35 and earlier) and Audio Port (versions 1.0.24 and earlier) allows authenticated attackers with network access to inject arbitrary commands through unsanitized input fields, achieving remote code execution at critical severity (CVSS 9.8).

MitigationApply vendor patches by updating UniFi Play PowerAmp to version 1.0.38 or later and UniFi Play Audio Port to version 1.1.9 or later to remediate the command injection vector.

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. Identify installed UniFi Play product
    Locate the UniFi Play application running on the system (PowerAmp or Audio Port). Check the application name or service identifier in the system inventory or running services.
    Affected if The product is UniFi Play PowerAmp or UniFi Play Audio Port
  2. Determine installed version number
    Access the product's web interface, admin console, or check the application binary/package version. Common methods: look at the About section in the UI, check the installed package version via system package manager, or query the application API if available.
    Affected if Version cannot be determined or is 1.0.35 or earlier for PowerAmp, or 1.0.24 or earlier for Audio Port
  3. Compare version to affected ranges
    If the version is identified, compare it to the affected ranges: PowerAmp 1.0.35 and earlier, Audio Port 1.0.24 and earlier.
    Affected if Installed version falls within or below these affected version numbers
  4. Verify network accessibility of the service
    Check if the product's web interface or API ports are exposed to the network. Review firewall rules, network configuration, and listening services to determine if the management interface can be reached remotely.
    Affected if The service is accessible from untrusted networks (not localhost or isolated management VLAN only)
  5. Confirm authentication is enabled
    Verify that authentication is required to access the product interface. Check if default credentials are in use or if strong authentication has been configured.
    Affected if The product allows unauthenticated access to input fields, or uses weak/default credentials

A user is affected if they have UniFi Play PowerAmp version 1.0.35 or earlier, or Audio Port version 1.0.24 or earlier, that is network-accessible with authentication configured.

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

Apply vendor patches by updating UniFi Play PowerAmp to version 1.0.38 or later and UniFi Play Audio Port to version 1.1.9 or later to remediate the command injection vector.

Recommended fix High confidence

UniFi Play PowerAmp: 1.0.38+ | UniFi Play Audio Port: 1.1.9+

  1. Identify which UniFi Play products (PowerAmp and/or Audio Port) are deployed in your environment
  2. Check the current installed version of each affected product
  3. For UniFi Play PowerAmp users: Upgrade to version 1.0.38 or later
  4. For UniFi Play Audio Port users: Upgrade to version 1.1.9 or later
  5. Obtain the updates from the official Ubiquiti download portal or through your UniFi Play controller interface
  6. Before upgrading, back up current configurations as a precautionary measure
  7. Apply the upgrade following standard Ubiquiti UniFi Play update procedures
  8. After upgrading, verify the new version is correctly installed and the service is operational
Caveat Review Ubiquiti release notes for each version to check for any configuration or feature changes that may affect your deployment

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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