Subscriber-level PHP object injection via unsafe deserialization
Published Dec 18, 2025 · Updated Dec 18, 2025
Deserialization of untrusted data in PDF Invoice Builder for WooCommerce 6.5.0 and earlier allows remote authenticated users to inject PHP objects. Published advisories do not identify the request parameter or code path that deserializes attacker-controlled input. Subscriber access is required, and file deletion, sensitive-data retrieval, or code execution requires a separate plugin or theme with a usable POP chain.
Summary
What happened
Deserialization of untrusted data in PDF Invoice Builder for WooCommerce 6.5.0 and earlier allows remote authenticated users to inject PHP objects. Published advisories do not identify the request parameter or code path that deserializes attacker-controlled input. Subscriber access is required, and file deletion, sensitive-data retrieval, or code execution requires a separate plugin or theme with a usable POP chain.
The record
- CVE
- CVE-2025-60083
- Published
- Dec 18, 2025
- Updated
- Dec 18, 2025
- Vendor
- add-ons.org
- Product
- PDF Invoice Builder for WooCommerce
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 18, 2025CVE publishedPublication date reported by the CVE source.
- Dec 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=<= 6.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo