How severe is GHSA-w8xh-93qh-35vw?

GHSA-w8xh-93qh-35vw has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-w8xh-93qh-35vw?

GHSA-w8xh-93qh-35vw affects the following packages: payload (npm). Ecosystems affected: npm.

How do I fix GHSA-w8xh-93qh-35vw?

Update payload to 0.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w8xh-93qh-35vw is resolved across your whole dependency graph.

How do I detect GHSA-w8xh-93qh-35vw in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for payload. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-w8xh-93qh-35vw if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-w8xh-93qh-35vw?

O3 pinpoints whether GHSA-w8xh-93qh-35vw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-w8xh-93qh-35vw actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-w8xh-93qh-35vw, 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 type of vulnerability is GHSA-w8xh-93qh-35vw?

GHSA-w8xh-93qh-35vw is classified as Unrestricted File Upload (CWE-434). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w8xh-93qh-35vw published, and has it been updated?

GHSA-w8xh-93qh-35vw was published on April 13, 2022 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-w8xh-93qh-35vw

CRITICAL

GHSA-w8xh-93qh-35vw is a critical-severity (CVSS 9.8) Unrestricted File Upload vulnerability in payload. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-w8xh-93qh-35vw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Unrestricted Upload of File with Dangerous Type in Payload

Also known asCVE-2022-27952

Published

Apr 13, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

payloadnpm

642Kdownloads / week

Description

An arbitrary file upload vulnerability in the file upload module of PayloadCMS v0.15.0 allows attackers to execute arbitrary code via a crafted SVG file.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`payload`	all versions	0.15.1

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.

An arbitrary file upload vulnerability in the file upload module of Payl…

youtube.comNVDApr 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for payload. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update payload to 0.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w8xh-93qh-35vw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w8xh-93qh-35vw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w8xh-93qh-35vw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An arbitrary file upload vulnerability in the file upload module of PayloadCMS v0.15.0 allows attackers to execute arbitrary code via a crafted SVG file.

O3 Security · Impact-Aware SCA

Is GHSA-w8xh-93qh-35vw in your dependencies?

O3 detects GHSA-w8xh-93qh-35vw 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 dependencies How O3 SCA works