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-62045 Overview
CVE-2026-62045 is a PHP Object Injection vulnerability in the ThemeREX Booklovers WordPress theme. The flaw results from deserialization of untrusted data [CWE-502] and affects all versions up to and including 2.13.0. An unauthenticated attacker can send crafted serialized payloads over the network to trigger object instantiation within the application.
When combined with a suitable Property-Oriented Programming (POP) chain from WordPress core or installed plugins, exploitation can lead to arbitrary code execution, file manipulation, or full site compromise. The vulnerability requires no authentication and no user interaction.
Critical Impact
Unauthenticated remote attackers can inject PHP objects into the Booklovers theme, enabling arbitrary code execution and full WordPress site takeover when a POP chain is present.
Affected Products
- ThemeREX Booklovers WordPress theme versions through 2.13.0
- WordPress sites running Booklovers alongside plugins that expose exploitable magic methods
- Any deployment of the Booklovers theme that has not been updated beyond 2.13.0
Discovery Timeline
- 2026-10-10 - CVE-2026-62045 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-62045
Vulnerability Analysis
The Booklovers theme passes attacker-controlled input to a PHP deserialization function such as unserialize() without validating the data source or structure. PHP deserialization reconstructs objects from a serialized string and automatically invokes magic methods such as __wakeup(), __destruct(), and __toString() on instantiated classes.
Attackers craft a serialized payload referencing classes already loaded by WordPress core, the active theme, or installed plugins. When deserialized, the magic methods on those classes execute attacker-controlled logic. This technique is known as a POP chain and can translate object injection into file writes, SQL execution, or arbitrary command execution.
Root Cause
The root cause is unsafe handling of serialized input in the Booklovers theme code. The theme accepts serialized data from an unauthenticated request vector and passes it directly to a deserialization routine. No integrity check, allow-list of permitted classes, or signed-payload mechanism is enforced.
Attack Vector
Exploitation occurs over the network against the WordPress HTTP interface. An attacker submits a crafted request containing a serialized PHP object to the vulnerable endpoint exposed by the Booklovers theme. The server deserializes the payload and instantiates the referenced classes, triggering the embedded POP chain. Successful exploitation yields code execution in the context of the PHP worker process.
For technical specifics, see the Patchstack Vulnerability Report.
Detection Methods for CVE-2026-62045
Indicators of Compromise
- HTTP request bodies or query parameters containing serialized PHP markers such as O:, a:, or s: sent to Booklovers theme endpoints
- Unexpected PHP file creation, modification of wp-config.php, or new administrator accounts in wp_users
- Outbound connections from the web server to unfamiliar hosts following suspicious POST requests
- Web shells or obfuscated PHP files in theme, plugin, or uploads directories
Detection Strategies
- Inspect web server access logs for requests to Booklovers theme paths containing serialized object patterns
- Monitor PHP error logs for deserialization warnings referencing missing classes or malformed input
- Deploy file integrity monitoring on wp-content/themes/booklovers/ and the broader WordPress install
- Use a web application firewall rule set that blocks serialized payloads in untrusted request parameters
Monitoring Recommendations
- Alert on creation of PHP files inside upload directories such as wp-content/uploads/
- Track administrator role assignments and option changes within WordPress audit logs
- Correlate anomalous outbound traffic from web hosts with inbound requests to vulnerable theme endpoints
How to Mitigate CVE-2026-62045
Immediate Actions Required
- Inventory all WordPress sites running the Booklovers theme and confirm installed versions
- Take affected sites offline or place them behind a WAF with virtual patching while remediation is in progress
- Audit WordPress installations for signs of prior exploitation, including unknown admin accounts and modified core files
- Rotate WordPress secrets in wp-config.php and all administrator credentials on sites that were exposed
Patch Information
The vendor advisory is tracked on Patchstack. Administrators should upgrade Booklovers beyond version 2.13.0 once a fixed release is available. Refer to the Patchstack Vulnerability Report for the latest fixed version and vendor guidance.
Workarounds
- Deactivate and remove the Booklovers theme on sites that cannot be upgraded immediately
- Restrict access to the WordPress site using IP allow-lists or authentication at the reverse proxy layer
- Deploy WAF rules that block serialized PHP object patterns in HTTP request parameters targeting theme endpoints
- Disable or restrict PHP functions that commonly appear in POP chains where feasible for the hosting environment
# Example WAF rule concept (ModSecurity) to block serialized PHP objects
SecRule ARGS "@rx (?:^|[^a-zA-Z0-9])O:\d+:\"[^\"]+\":\d+:\{" \
"id:1026062045,phase:2,deny,status:403,msg:'Possible PHP object injection payload (CVE-2026-62045)'"
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

