Export All Posts, Products, Orders & Users | WP Ultimate Exporter | WordPress CSV Export <= 3.0 - Authenticated (Custom Role+) PHP Object Injection
Strategic Overview
- Status
- Patched in 3.1
- Affected Plugin
- Export All Posts, Products, Orders & Users | WP Ultimate Exporter | WordPress CSV Export
- Affected Version
<= 3.0- CVSS
- 7.5High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2026-103348
At a glance
CVE-2026-103348 is a high-severity Deserialization of Untrusted Data vulnerability in the Export All Posts, Products, Orders & Users WordPress plugin, affecting versions <= 3.0. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Custom Role level or above. The issue is fixed in version 3.1; sites on affected versions should update now. Disclosed October 2026, reported by Ananda Dhakal.
Vulnerability Overview
The Export All Posts, Products, Orders & Users | WP Ultimate Exporter | WordPress CSV Export plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.0. This is due to deserialization of untrusted input. This makes it possible for authenticated attackers, with custom role-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
Reaching this weakness in Export All Posts, Products, Orders & Users <= 3.0 takes an account at Custom Role level or above. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Export All Posts, Products, Orders & Users the fix is 3.1: builds <= 3.0 are affected, anything from 3.1 onward is not.
Remediation
Update to version 3.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Custom Role access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Export All Posts, Products, Orders & Users 3.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Export All Posts, Products, Orders & Users | WP Ultimate Exporter | WordPress CSV Export
- 9.8CVE-2016-11000: Export WordPress Data with Advanced… SQL Injection
CVE-2016-11000 - 8.8CVE-2018-20968: Export WordPress Data with Advanced Filters CSRF
CVE-2018-20968 - 7.5CVE-2024-12315: Export All Posts Information Disclosure
CVE-2024-12315 - 6.5CVE-2025-13606: Export All Posts CSRF
CVE-2025-13606 - 6.1WP Ultimate Exporter < 1.1 Reflected Cross-Site Scripting
- 5.3CVE-2023-2487: WP Ultimate Exporter <= 2.4.1 Information Disclosure
CVE-2023-2487 - 4.9CVE-2025-24611: WP Ultimate Exporter <= 2.9 Arbitrary File Read
CVE-2025-24611 - 4.1CVE-2024-56278: WP Ultimate Exporter <= 2.9.1 Remote Code Execution
CVE-2024-56278
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C