Safeguard
Vulnerability Analysis•

CVE-2023-24676: High Disputed Code Execution in ProcessWire

A disputed report says ProcessWire 3.0.210 can run code via the module download URL. High, CVSS 7.2, admin only. Limit admin rights and module installs.

Safeguard Security Team
3 min read

CVE-2023-24676 is a high severity code injection report (CVSS 7.2) against ProcessWire 3.0.210. The record says an attacker can run arbitrary code through the download_zip_url parameter when a new module is installed. The entry is disputed, because exploitation needs admin access and admins may install any module by design.

What's affected

  • ProcessWire version 3.0.210, per the record. No other versions are named.
  • No fixed version is listed in the record. Because the CVE is disputed, the vendor may not treat it as a defect.
  • Attack requirements: network access and high privileges, meaning an administrator account, no user interaction.
  • Severity: CVSS 3.1 score 7.2 High, vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H.

The only reference in the record is a Medium post. Our fetch tool was blocked from it, so we could not read the researcher's description. The dispute note in the record is the one fact we can state with confidence: it says exploitation requires the attacker to be an admin, and that admins can install any module that contains arbitrary code.

How to check if you're exposed

Check the ProcessWire version from the admin interface, or from your deployment records. Then list who holds the superuser role and who can install modules:

grep -rn "moduleInstall" site/config.php wire/config.php

The command shows whether your site config restricts module installation. Check the ProcessWire documentation for the exact settings in your version. Also look at the list of users with the superuser role in the admin and confirm each one is expected.

What to do now

  1. Confirm which sites run ProcessWire and note the version of each.
  2. List superuser and other admin level accounts, and remove any that are not needed.
  3. Turn on strong passwords and two factor sign in for administrators if your setup supports it.
  4. Review the installed modules and remove ones you do not recognize.
  5. Read the ProcessWire documentation on restricting module installation, and apply the settings that match your risk.

Why it matters

The weakness is code injection (CWE-94 (Code Injection)). Installing a module from a URL means downloading code and running it. In that sense the feature works as designed, and the dispute note says so: an administrator is meant to be able to install code.

That makes this entry a useful reminder rather than a classic bug. The real control is who has admin rights. If an attacker obtains an admin session, the attack surface of the CMS includes everything that admin can do, including module installs. Guard admin accounts, review module lists, and limit where modules can come from. CISA has not listed this CVE in its Known Exploited Vulnerabilities catalog, according to the record we hold, and none of the pages we read said it is being exploited.

Quick check

Why is the CVE disputed?

The record says exploitation needs admin access, and a ProcessWire admin is allowed to install any module, including one with arbitrary code.

Should I still act?

Yes, but on admin hygiene rather than on a patch. Limit and monitor admin accounts, and review installed modules.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.