Vulnerability

CVE-2010-5330

Critical· 9.8KEVCVSS9.8EPSS43%

.rules3/5

Ubiquiti AirOS Command Injection Vulnerability

Certain Ubiquiti devices contain a command injection vulnerability via a GET request to stainfo.cgi.

Threat signal

100/100

Severe

Severity

critical

CVSS

9.8

EPSS

43%

Active

KEV

CISA KEV — actively exploited

1499d overdue

AffectedUbiquiti — AirOS

Added to KEV

2022-04-15

Federal patch due (BOD 22-01)

2022-05-06

Required action (CISA verbatim)

Apply updates per vendor instructions.

Vendor advisory + references

https://nvd.nist.gov/vuln/detail/CVE-2010-5330

CISA description: “Certain Ubiquiti devices contain a command injection vulnerability via a GET request to stainfo.cgi.”

CVSS

v3.1Open in FIRST calculator →

9.8/ 10CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack VectorNetworkExploitable remotely over the internet — no local access needed.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredNoneUnauthenticated — no credentials needed.
User InteractionNoneFully automated — no victim action needed.
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactHighTotal disclosure of sensitive data.
Integrity ImpactHighTotal compromise of integrity — full data modification possible.
Availability ImpactHighTotal loss of availability — full DoS possible.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

42.8%

probability of exploitation in next 30 days

p98

higher than 98% of all CVEs

3-day trend↑ 0pp

Above the FIRST 'patch on a priority schedule' threshold.

Vendor VEX

No VEX statements published for CVE-2010-5330. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCAct

Active exploitation with total impact on essential/support systems

exploitation: active
automatable: yes
impact: total
mission: support

Lifecycle

2022-04-15Added to CISA KEVransomware: Unknown
2022-04-15Published
2022-05-06Federal patch due (BOD 22-01)
2026-06-12Last modified1 source

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.