# CVE-2025-60790: ProcessWire CMS vulnerable to resource-exhaustion Denial of Service > A low-privileged user can cause resource exhaustion and denial of service by uploading a crafted ZIP file to the Language Support module. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 21 Oct 2025 - **Updated:** 27 Oct 2025 - **Also known as:** GHSA-9p44-q66p-xm6p ## What is CVE-2025-60790? CVE-2025-60790 is a medium-severity denial of service vulnerability in n/a, published on 21 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2025-60790? 2 open source packages ship an affected version, including processwire/processwire. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `processwire/processwire` | Packagist | All versions to 3.0.246 | None | | `processwire/processwire` | Packagist | All versions to 3.0.246 | None | Products: Processwire Processwire. ## How do I fix CVE-2025-60790? No fix has been published for CVE-2025-60790 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-60790 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60790 exists. ## Other vulnerabilities in n/a - [CVE-2020-27467](https://insights.sbomify.com/CVE-2020-27467/): Path traversal in n/a (high 7.5) - [CVE-2023-24676](https://insights.sbomify.com/CVE-2023-24676/): Arbitrary Code Execution in Processwire (high 7.2) - [CVE-2022-40488](https://insights.sbomify.com/CVE-2022-40488/): ProcessWire vulnerable to Cross-Site Request Forgery (medium 6.5) - [CVE-2022-40487](https://insights.sbomify.com/CVE-2022-40487/): ProcessWire vulnerable to Cross-site Scripting (medium 6.1) - [CVE-2024-41597](https://insights.sbomify.com/CVE-2024-41597/): ProcessWire Cross Site Request Forgery vulnerability (medium 4.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-60790 and fix it if it is affected. What it is: CVE-2025-60790 is a medium-severity denial of service vulnerability in n/a, published on 21 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60790 exists. Affected packages and fixed versions: - processwire/processwire (Packagist): affected all versions up to 3.0.246; no fix listed - processwire/processwire (Packagist): affected all versions up to 3.0.246; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-60790/ (Markdown: https://insights.sbomify.com/CVE-2025-60790/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-60790 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-60790 - OSV: https://osv.dev/vulnerability/CVE-2025-60790 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-60790/ Summaries are generated and may contain mistakes; the official description above is the record.