GHSA-gmwr-9j4p-96vm — processwire/processwire
MEDIUMGHSA-gmwr-9j4p-96vm is a medium-severity (CVSS 6.8) vulnerability in processwire/processwire. No vendor fix is recorded yet; mitigation options are listed below.
ProcessWire: server-side request forgery vulnerability in the admin panel's 'Add Module From URL' feature
Real-World Exposure
processwire/processwireReal-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 version 3.0.255 and prior contain a server-side request forgery vulnerability in the admin panel's 'Add Module From URL' feature that allows authenticated administrators to supply arbitrary URLs to the module download parameter, causing the server to issue outbound HTTP requests to attacker-controlled internal or external hosts. Attackers can exploit differentiable error messages returned by the server to perform reliable internal network port scanning, host enumeration across RFC-1918 ranges, and potential access to cloud instance metadata endpoints.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | processwire/processwire | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
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
No patched version of processwire/processwire has shipped for GHSA-gmwr-9j4p-96vm yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gmwr-9j4p-96vm can be triaged on real exposure rather than presence alone.
Tailored to GHSA-gmwr-9j4p-96vm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-gmwr-9j4p-96vm in your dependencies?
O3 Security finds GHSA-gmwr-9j4p-96vm across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.