# CVE-2023-24676: Arbitrary Code Execution in Processwire

> Administrators can execute arbitrary code via the module installation feature, though this is disputed as it aligns with intended admin privileges.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2024
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-2cvg-w29m-j8xc

## What is CVE-2023-24676?

CVE-2023-24676 is a high-severity code injection vulnerability in n/a, published on 24 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue found in ProcessWire 3.0.210 allows attackers to execute arbitrary code and install a reverse shell via the download_zip_url parameter when installing a new module. NOTE: this is disputed because exploitation requires that the attacker is able to enter requests as an admin; however, a ProcessWire admin is intentionally allowed to install any module that contains any arbitrary code.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-24676?

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.210 | None |
| `processwire/processwire` | Packagist | All versions to 3.0.210 | None |

Products: Processwire Processwire.

## How do I fix CVE-2023-24676?

No fix has been published for CVE-2023-24676 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-24676 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24676 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-2025-60790](https://insights.sbomify.com/CVE-2025-60790/): ProcessWire CMS vulnerable to resource-exhaustion Denial of Service (medium 6.5)
- [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-2023-24676 and fix it if it is affected.

What it is: CVE-2023-24676 is a high-severity code injection vulnerability in n/a, published on 24 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24676 exists.

Affected packages and fixed versions:
- processwire/processwire (Packagist): affected all versions up to 3.0.210; no fix listed
- processwire/processwire (Packagist): affected all versions up to 3.0.210; 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-2023-24676/ (Markdown: https://insights.sbomify.com/CVE-2023-24676/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-24676
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-24676
- OSV: https://osv.dev/vulnerability/CVE-2023-24676

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-24676/
Summaries are generated and may contain mistakes; the official description above is the record.