Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-104764 Overview
The Post Export Import with Media plugin for WordPress contains a PHP Object Injection vulnerability affecting all versions up to and including 1.17.1. The flaw stems from unsafe deserialization of untrusted input within the plugin's page handler component. Authenticated attackers with administrator-level access or higher can inject arbitrary PHP objects into the application. The plugin itself does not ship a Property-Oriented Programming (POP) chain, so exploitation depends on another installed plugin or theme providing one. When a POP chain is present, attackers can delete arbitrary files, exfiltrate sensitive data, or execute code on the server.
Critical Impact
Authenticated administrators can trigger PHP Object Injection that, when combined with a POP chain from another installed component, enables arbitrary file deletion, data disclosure, or remote code execution.
Affected Products
- Post Export Import with Media plugin for WordPress — all versions up to and including 1.17.1
- WordPress installations with vulnerable plugin activated
- Any WordPress site hosting an additional plugin or theme exposing a POP gadget chain
Discovery Timeline
- 2026-10-14 - CVE-2026-104764 published to NVD
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-104764
Vulnerability Analysis
The vulnerability is a PHP Object Injection flaw categorized under CWE-502: Deserialization of Untrusted Data. The plugin passes attacker-controlled input into PHP's unserialize() function without validating or restricting the resulting object graph. During deserialization, PHP reconstructs objects and invokes magic methods such as __wakeup() and __destruct(). An attacker who can supply the serialized payload controls the properties of those reconstructed objects.
The plugin alone has no exploitable gadget chain. Exploitation becomes practical when another installed plugin or theme defines classes with dangerous magic methods that can be chained into a POP chain. The combined impact ranges from arbitrary file deletion to remote code execution depending on the available gadgets.
Root Cause
The root cause is the use of unsafe deserialization on input reachable through administrative plugin functionality in includes/class-page-handler.php. Public references point to deserialization sinks at lines 230, 370, 646, and 877 of the file in tag 1.17.1. The handler accepts serialized data and reconstructs PHP objects without a safe allowlist or alternative format such as JSON.
Attack Vector
Exploitation requires authenticated access at the administrator role or above and is network-reachable through the WordPress admin interface. The attacker submits a crafted serialized string to the vulnerable plugin endpoint. The handler deserializes the payload, instantiating attacker-chosen classes. If a POP chain exists in any installed plugin, theme, or dependency, the chain executes during object construction or destruction. The resulting behavior depends on the gadget, including file writes, file deletions, SQL execution through loaded ORM classes, or command execution through callable properties.
No verified public proof-of-concept code is available. See the Wordfence Vulnerability Report and the fixed-code WordPress Changeset 3726397 for technical details.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-104764
Indicators of Compromise
- POST requests to admin-ajax endpoints associated with the Post Export Import with Media plugin containing serialized PHP payloads beginning with O:, a:, or s: patterns.
- Unexpected file creation, modification, or deletion in wp-content/uploads/ or plugin directories following administrator sessions.
- PHP error log entries referencing __wakeup, __destruct, or unserialize() warnings tied to class-page-handler.php.
- New or modified administrator accounts created shortly after plugin interaction.
Detection Strategies
- Inspect web server access logs for administrator requests to the plugin's handler containing URL-encoded serialized object markers.
- Monitor the WordPress database wp_options and plugin option tables for stored serialized payloads referencing unexpected class names.
- Compare installed plugin files against the official repository checksums to identify tampering.
- Review audit logs for administrator role additions, permission changes, and plugin configuration edits.
Monitoring Recommendations
- Enable WordPress audit logging to track administrator activity, plugin configuration changes, and option updates.
- Alert on PHP runtime warnings referencing deserialization errors from plugin files.
- Monitor outbound connections from the web server for unexpected destinations following administrator plugin usage.
- Track file integrity across wp-content/plugins/post-export-import-with-media/ and the broader WordPress installation.
How to Mitigate CVE-2026-104764
Immediate Actions Required
- Update the Post Export Import with Media plugin to a version newer than 1.17.1 once published by the vendor.
- Audit all administrator accounts and remove unused or stale privileged users to reduce the authenticated attack surface.
- Enforce multi-factor authentication for all WordPress administrator and editor accounts.
- Inventory installed plugins and themes to identify components known to expose POP gadget chains.
Patch Information
The fix is published in WordPress Changeset 3726397, which modifies includes/class-page-handler.php to remove the unsafe deserialization paths. Site operators should pull the latest version from the WordPress Plugin Repository and verify the file no longer calls unserialize() on user-controlled input. Review the vendor summary in the Wordfence Vulnerability Report for upgrade guidance.
Workarounds
- Deactivate and remove the Post Export Import with Media plugin until the patched version is installed.
- Restrict administrator access through IP allowlists on the wp-admin/ path at the web server or WAF layer.
- Deploy a WordPress-aware WAF ruleset that blocks requests containing serialized PHP object markers to the plugin endpoints.
- Review installed plugins and themes for known POP gadget chains and remove unneeded components.
# Configuration example: nginx rule to block serialized PHP payloads to the vulnerable plugin endpoint
location ~ ^/wp-admin/admin(-ajax)?\.php$ {
if ($arg_page ~* "post-export-import-with-media") {
if ($request_body ~* "(^|&)[^=]+=O:[0-9]+:\"") {
return 403;
}
}
include fastcgi_params;
fastcgi_pass php-upstream;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

