WordPress security changelog
CRITICAL CVE-2026-104801 Received

PPOM – Product Addons & Custom Fields for WooCommerce: Filesystem traversal

An unauthenticated caller can supply an unvalidated path to rename_files, moving a server file into the public wp-content/uploads/ppom_files/confirmed/ directory. This both removes the original and exposes the unchanged copy. Removing critical configuration can create a conditional takeover or code-execution chain; that is not automatic. The narrative describes file disclosure although the supplied vector reports C:N. Affected versions: <= 34.0.10. The matching official changelog confirms 34.0.11 as fixed for this CVE.

CVE / CNA score 9.1 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
PPOM – Product Addons & Custom Fields for WooCommerce
Plugin slug
woocommerce-product-addon
Affected
<= 34.0.10
Safe version
34.0.11
Published
Oct 10, 2026
Weakness
CWE-22 — Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

This CVE was published Oct 10, 2026 and is one of 8 known issues for this plugin.

What to do

Update, patch or deactivate.

Update to 34.0.11 or a later supported release. Application-level remediation: Resolve and confine both source and destination paths to authorized PPOM uploads, verify file ownership, and reject attempts to relocate configuration or other application files.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

References

Primary and upstream sources