VYPR
High severity7.2NVD Advisory· Published Jun 15, 2026· Updated Jun 15, 2026

CVE-2026-39472

CVE-2026-39472

Description

PHP Object Injection in WooCommerce PDF Invoices & Packing Slips plugin allows unauthenticated attackers to execute arbitrary code before version 5.9.0.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

PHP Object Injection in WooCommerce PDF Invoices & Packing Slips plugin allows unauthenticated attackers to execute arbitrary code before version 5.9.0.

Vulnerability

The WooCommerce PDF Invoices & Packing Slips plugin for WordPress is vulnerable to PHP Object Injection in versions before 5.9.0. The vulnerability exists due to insecure deserialization of user-supplied input, allowing an attacker to inject arbitrary PHP objects. No authentication is required for exploitation, and the attack vector is through crafted input [1].

Exploitation

An attacker can exploit this vulnerability by sending a specially crafted request containing a serialized PHP object to the vulnerable plugin endpoint. The plugin deserializes the object, enabling the attacker to trigger arbitrary code execution if a suitable POP chain is present in the environment [1].

Impact

Successful exploitation could lead to arbitrary code execution, SQL injection, path traversal, denial of service, or other impacts depending on the available POP chain. The attacker could gain full control of the affected WordPress site, leading to complete compromise [1].

Mitigation

Update to version 5.9.0 or later to resolve the vulnerability. Patchstack users can enable auto-update for vulnerable plugins. Until the update is applied, Patchstack provides a mitigation rule to block attacks [1].

AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.