VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

processwire/processwire: vulnerability history, versions and safety

processwire/processwire is a package in the Packagist ecosystem. Vulert records 6 vulnerabilities for it across 22 releases, from Oct 2022 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H1 M4 L1
i
6 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 16 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all processwire/processwire vulnerabilities

Vulert verdict on processwire/processwire i

Updated on 23 Oct 2026

Careful: 6 of the 6 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 6 vulnerabilities on record across 3 years, 1 in the last year.

What to do: Plan around the 6 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 6 over 3 years · 1 in the last year i
  • Latest disclosure 16 Apr 2026 i
  • Highest CVSS 7.2 i
  • With no published fix 6 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for processwire/processwire, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
3.0.255 M1 No Details →
3.0.246 M2 No Details →
3.0.244 M2 No Details →
3.0.227 M2 L1 No Details →
3.0.226 M2 L1 No Details →
3.0.210 H1 M2 L1 No Details →
3.0.200 H1 M4 L1 No Details →
3.0.184 H1 M4 L1 No Details →
3.0.165 H1 M4 L1 No Details →
3.0.164 H1 M4 L1 No Details →
3.0.148 H1 M4 L1 No Details →
3.0.123 H1 M4 L1 No Details →
3.0.98 H1 M4 L1 No Details →
3.0.96 H1 M4 L1 No Details →
3.0.62 H1 M4 L1 No Details →
3.0.61 H1 M4 L1 No Details →
3.0.42 H1 M4 L1 No Details →
3.0.41 H1 M4 L1 No Details →
3.0.39 H1 M4 L1 No Details →
3.0.36 H1 M4 L1 No Details →
3.0.35 H1 M4 L1 No Details →
3.0.34 H1 M4 L1 No Details →

Newest 22 of 22 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2024 2
  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for processwire/processwire

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2023-24676: Arbitrary Code Execution in Processwire 7.2 high No fix published 24 Jan 2024
CVE-2026-40500: ProcessWire Server-Side Request Forgery Vulnerability in Admin Panel 6.8 medium No fix published 16 Apr 2026
CVE-2022-40488: ProcessWire vulnerable to Cross-Site Request Forgery 6.5 medium No fix published 31 Oct 2022
CVE-2022-40487: ProcessWire vulnerable to Cross-site Scripting 6.1 medium No fix published 31 Oct 2022
CVE-2025-60790: ProcessWire CMS Resource-Exhaustion Denial of Service Vulnerability 5.6 medium No fix published 21 Oct 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About processwire/processwire

Is processwire/processwire safe to use?

Vulert records 6 vulnerabilities for processwire/processwire in Packagist: 0 critical, 1 high, 4 medium and 1 low. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does processwire/processwire have?

6 vulnerabilities are recorded for processwire/processwire in the Packagist ecosystem: 0 critical, 1 high, 4 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new processwire/processwire vulnerabilities disclosed?

1 vulnerability was recorded for processwire/processwire in the last 12 months, and the oldest entry in this database dates to 31 Oct 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of processwire/processwire are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor processwire/processwire for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the processwire/processwire version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.