How severe is GHSA-xq6j-x8pq-g3gr?

GHSA-xq6j-x8pq-g3gr has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xq6j-x8pq-g3gr?

GHSA-xq6j-x8pq-g3gr affects the following packages: appium-desktop (npm). Ecosystems affected: npm.

How do I fix GHSA-xq6j-x8pq-g3gr?

No fixed version has been published for GHSA-xq6j-x8pq-g3gr yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is GHSA-xq6j-x8pq-g3gr actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-xq6j-x8pq-g3gr, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-xq6j-x8pq-g3gr?

GHSA-xq6j-x8pq-g3gr has an EPSS (Exploit Prediction Scoring System) score of 92.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-xq6j-x8pq-g3gr?

GHSA-xq6j-x8pq-g3gr is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-xq6j-x8pq-g3gr?

A Nuclei detection template exists for GHSA-xq6j-x8pq-g3gr, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-xq6j-x8pq-g3gr published, and has it been updated?

GHSA-xq6j-x8pq-g3gr was published on May 2, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-xq6j-x8pq-g3gr

CRITICAL

appium-desktop OS Command Injection vulnerability

Also known asCVE-2023-2479

Published

May 2, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

92.7%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦appium-desktop

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

appium-desktop v1.14.1 and prior is vulnerable to OS Command Injection.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`appium-desktop`	all versions	No fix

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

OS Command Injection in GitHub repository appium/appium-desktop prior to…

huntr.devNVDMay 2023

Frequently Asked Questions

appium-desktop v1.14.1 and prior is vulnerable to OS Command Injection.

O3 Security · Impact-Aware SCA

Is GHSA-xq6j-x8pq-g3gr in your stack?

O3 detects GHSA-xq6j-x8pq-g3gr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works

CVSS Score

9.8/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction

None

S:Scope

Unchanged

C:Confidentiality

High

I:Integrity

High

A:Availability

High

Raw vector

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

CWE Classification

CWE-78OS Command Injection

Weaponization

OpenSSF Scorecard

Package health score

appium-desktop

3.0/10

Code-Review3/10

Maintained0/10

Branch-Protection0/10

Assessed Jun 8, 2026

Timeline

Disclosed

May 2, 2023

First exploit

May 9, 2023

7 days after disclosure — rapid exploitation

Last updated

Nov 8, 2023

Identifiers

GHSA-xq6j-x8pq-g3gr

References

Advisorynvd.nist.gov Webgithub.com Webhuntr.dev Packagegithub.com

Data from OSV.dev, enriched by O3 Security. Refreshed hourly.