CVE-2026-104801

PPOM <= 34.0.10 - Unauthenticated Arbitrary File Deletion via 'ppom[fields][<data_name>][n][org]' Parameter

2026-10-09 17:51
whatm

Strategic Overview

Status
Patched in 34.0.11
Affected Plugin
PPOM – Product Addons & Custom Fields for WooCommerce
Affected Version
<= 34.0.10
CVSS
9.1Critical
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2026-104801
View all PPOM – Product Addons & Custom Fields for WooCommerce vulnerabilities

At a glance

CVE-2026-104801 is a critical-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the PPOM WordPress plugin, affecting versions <= 34.0.10. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 34.0.11; sites on affected versions should update now. Disclosed October 2026, reported by whatm.

Vulnerability Overview

The PPOM – Product Addons & Custom Fields for WooCommerce plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the rename_files function in all versions up to, and including, 34.0.10 This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The relocated file is moved byte-identically into the publicly accessible wp-content/uploads/ppom_files/confirmed/ directory, meaning the attack also results in arbitrary file read for any web-readable file on the server.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in PPOM <= 34.0.10 takes no account at all. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For PPOM the fix is 34.0.11: builds <= 34.0.10 are affected, anything from 34.0.11 onward is not.

Remediation

Update to version 34.0.11, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: PPOM 34.0.11 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-104801https://www.wordfence.com/threat-intel/vulnerabilities/id/650b510f-dc13-4ba4-af68-187f516b3051https://nvd.nist.gov/vuln/detail/CVE-2026-104801

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C