CVE-2025-60790: processwire · n/a
Affects processwireSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.0.246 when convenient.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.0.246
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade processwire/processwire to 3.0.246.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubprocesswire/processwirepkg:github/processwire/processwireOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately restrict 'lang-edit' privileges to only trusted and necessary users to reduce the attack surface. 2. Implement strict file upload controls, including limiting allowed file types, maximum file sizes, and scanning uploaded ZIP files before extraction. 3. Configure server resource limits (CPU, memory, disk quota) for the CMS process to prevent resource exhaustion from impacting the entire system. 4. Monitor logs and system metrics for unusual spikes in resource usage or failed extraction attempts. 5. If possible, disable automatic extraction of ZIP files in the Language Support module until a patch is available. 6. 7. Employ web application firewalls (WAF) with custom rules to detect and block suspicious ZIP uploads. 8. Conduct regular security audits and penetration testing focusing on file upload functionalities. 9. Educate administrators and users with elevated privileges about the risks of uploading untrusted archives. 10. Consider isolating the CMS environment using containerization or sandboxing to limit the blast radius of potential DoS attacks.
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.