Is processwire/processwire vulnerable?

Composer processwire/processwire has 6 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

6advisories
0critical
0on CISA KEV
6no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2023-24676Arbitrary Code Execution in Processwirehigh7.2<=3.0.210–
CVE-2022-40487ProcessWire vulnerable to Cross-site Scriptingmedium6.1<=3.0.200–
CVE-2025-60790ProcessWire CMS vulnerable to resource-exhaustion Denial of Servicemedium0.0<=3.0.246–
CVE-2022-40488ProcessWire vulnerable to Cross-Site Request Forgerymedium6.5<=3.0.200–
CVE-2024-41597ProcessWire Cross Site Request Forgery vulnerabilitymedium4.2<=3.0.229–
CVE-2026-40500ProcessWire: server-side request forgery vulnerability in the admin panel's 'Add Module From URL' featuremedium6.8<=3.0.255–

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.