How severe is GHSA-9p44-q66p-xm6p?

No CVSS score has been assigned to GHSA-9p44-q66p-xm6p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9p44-q66p-xm6p?

GHSA-9p44-q66p-xm6p affects the following packages: processwire/processwire (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-9p44-q66p-xm6p?

The records we use list no patched version of processwire/processwire for GHSA-9p44-q66p-xm6p. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-9p44-q66p-xm6p in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for processwire/processwire, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9p44-q66p-xm6p if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-9p44-q66p-xm6p actively exploited in the wild?

No public exploit code has been indexed for GHSA-9p44-q66p-xm6p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-9p44-q66p-xm6p?

GHSA-9p44-q66p-xm6p has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-9p44-q66p-xm6p?

GHSA-9p44-q66p-xm6p is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9p44-q66p-xm6p published, and has it been updated?

GHSA-9p44-q66p-xm6p was published on October 21, 2025 and was last updated on October 27, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

ProcessWire CMS vulnerable to resource-exhaustion Denial of ServiceGHSA-9p44-q66p-xm6p

GHSA-9p44-q66p-xm6p is a Uncontrolled Resource Consumption vulnerability in processwire/processwire. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2025-60790

Published

Oct 21, 2025

Updated

Oct 27, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9p44-q66p-xm6p.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘processwire/processwire

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

Description

ProcessWire CMS 3.0.246 allows a low-privileged user with lang-edit to upload a crafted ZIP to Language Support that is auto-extracted without limits prior to validation, enabling resource-exhaustion Denial of Service.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`processwire/processwire`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

processwireprocesswire

≤ 3.0.246

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for processwire/processwire, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of processwire/processwire for GHSA-9p44-q66p-xm6p. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-9p44-q66p-xm6p in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works