# CVE-2026-40500: ProcessWire: server-side request forgery vulnerability in the admin panel's 'Add Module From URL' feature


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 15 Apr 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-gmwr-9j4p-96vm

## What is CVE-2026-40500?

CVE-2026-40500 is a vulnerability in processwire/processwire, published on 15 Apr 2026. 

### Official description

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. The "Add Module from URL" feature requires superuser privileges (root-equivalent in ProcessWire) who already has unrestricted arbitrary code execution via standard module upload, making the SSRF vector incapable of providing incremental attack surface. The feature is also disabled by default and requires direct filesystem access to enable.

## Which versions are affected by CVE-2026-40500?

2 open source packages ship an affected version, including processwire/processwire.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `processwire/processwire` | Packagist | All versions to 3.0.255 | None |
| `processwire/processwire` | Packagist | All versions to 3.0.255 | None |

## How do I fix CVE-2026-40500?

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

## Is CVE-2026-40500 being exploited?

There is no known exploitation of CVE-2026-40500 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40500 and fix it if it is affected.

What it is: CVE-2026-40500 is a vulnerability in processwire/processwire, published on 15 Apr 2026. 
Exploitation: There is no known exploitation of CVE-2026-40500 in the wild and no public exploit code.

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

## Sources

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

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