EUVD-2026-96508
GHSA-mjr4-xvvg-63x3
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Invetex <= 2.18
-
DeliverySend crafted serialized PHP object to vulnerable endpoint
-
ExploitTrigger unserialize() of attacker input
-
ExecutionPOP gadget chain invokes magic methods
-
ImpactCompromise site integrity, data, or availability
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that a WordPress site be running the ThemeRex Invetex theme at version 2.18 or earlier, with a theme endpoint that deserializes attacker-controlled input reachable without authentication (consistent with PR:N/UI:N). The practical limiting factor is the CWE-502 nature of the flaw: achieving the full C:H/I:H/A:H impact depends on a usable PHP POP gadget chain being present in the theme, an active plugin, or WordPress core - object injection alone does not guarantee code execution if no exploitable chain is reachable. No special non-default configuration is documented as required, and no user interaction or authentication is needed. |
| Impact | All provided signals point to a high-severity issue but with important caveats. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) indicates remote, unauthenticated, low-complexity exploitation with full confidentiality/integrity/availability impact, and the PR:N metric confirms no authentication is required. However, EPSS, CISA KEV, and SSVC data were NOT provided, and no public POC was referenced - so exploitation probability and automatability cannot be assessed from the input. This is a PHP Object Injection / insecure deserialization flaw (CWE-502): the real-world impact (C:H/I:H/A:H) is contingent on the presence of a usable POP gadget chain in the Invetex theme or in co-installed plugins/WordPress core. If no exploitable gadget chain is reachable, practical impact may be substantially lower than the 9.8 implies, making the CVSS a worst-case ceiling rather than a confirmed outcome. Net: treat as a genuine priority for any site running Invetex <= 2.18 because it is unauthenticated and network-reachable, but note the absence of exploitation-probability signals and the gadget-chain dependency before assuming guaranteed RCE. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker submits crafted serialized PHP data to an Invetex theme endpoint that passes attacker input to unserialize(). If a suitable POP gadget chain exists in the theme, active plugins, or WordPress core, the injected object triggers magic methods leading to file operations, SQL manipulation, or code execution. No public exploit code was identified at time of analysis, and because AC:L/PR:N/UI:N the attack needs no authentication, user interaction, or complex preconditions beyond reaching the vulnerable endpoint. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Unauthenticated PHP object injection in the ThemeRex Invetex WordPress theme affects versions 2.18 and earlier, allowing remote attackers to supply crafted serialized input to a theme endpoint that performs unsafe deserialization. Successful exploitation can lead to full compromise of the confidentiality, integrity, and availability of the affected site, but the practical ceiling depends on whether a usable PHP POP gadget chain exists in the theme, an active plugin, or WordPress core. No public exploit code or confirmed active exploitation was identified at time of analysis, and the CVSS score should be weighed against the assessed AC:H rather than the reported AC:L.
RemediationAI
Vendor-released patch version is not specified in the available intelligence, so administrators should first check the Patchstack advisory at https://patchstack.com/database/wordpress/theme/invetex/vulnerability/wordpress-invetex-theme-2-18-php-object-injection-vulnerability?_s_id=cve and the ThemeRex release channel for the first Invetex build above 2.18 and upgrade to it as soon as it is published; if no fixed version is yet available, treat the theme as unfixable in place. In that case, the most effective compensating control is to deactivate the Invetex theme and switch to a maintained theme - this removes the attack surface entirely but obviously changes site appearance. If deactivation is not possible, block unauthenticated requests to any theme-specific endpoint that accepts serialized input (for example via WAF rules matching parameter values containing 'O:' or 'a:' serialization markers, or by denying direct access to the theme's AJAX and REST handlers), accepting that this is signature-based and may be bypassed by encoding tricks. Additionally, reduce gadget-chain availability by keeping all plugins and WordPress core patched and minimizing the number of active plugins that ship unserialize-capable classes; hardening PHP with open_basedir, disable_functions for exec-type calls, and a restrictive WAF provides defense in depth but does not correct the underlying deserialization flaw. Continue monitoring the advisory for a patched release and apply it immediately once published.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is classified as CWE-502 (Deserialization of Untrusted Data) and resides in the ThemeRex Invetex theme, which is distributed through the WordPress theme ecosystem and is tracked by the CPE cpe:2.3:a:themerex:invetex:*:*:*:*:*:*:*:* (all versions up to and including 2.18). Attack surface is any theme-reachable endpoint that passes attacker-supplied data into PHP's unserialize() or an equivalent object-instantiation routine without validation; this is common in WordPress themes that accept base64-encoded or otherwise encoded serialized payloads via query parameters, AJAX handlers (admin-ajax.php), or REST routes registered by the theme. Because the vector is PR:N/UI:N, the endpoint is reachable without authentication and without victim interaction, making it a pure network attack against any site running the vulnerable theme. Object injection in PHP is only a vulnerability primitive: impact is realized when the deserialized data reaches a magic method (__wakeup, __destruct, __toString, etc.) on a class whose property values are attacker-controlled, forming a POP gadget chain that terminates in a dangerous sink such as file write, command execution, or arbitrary option update. The gap between the reported CVSS 9.8 (AC:L) and our assessed 9.8 (AC:H) reflects exactly this uncertainty: the attacker must locate a viable gadget chain in the theme itself, in a concurrently active plugin, or in WordPress core, which is not guaranteed and varies by site configuration.
Know when PHP gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Network, unauthenticated, no interaction per vendor vector, but PHP object injection impact is contingent on a reachable POP gadget chain, so AC:H rather than AC:L.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated PHP Object Injection in Invetex <= 2.18 versions.
Executive ViewAI
Every public website running the ThemeRex Invetex WordPress theme at version 2.18 or earlier carries a critical, remote-reachable flaw that can hand an attacker full control of the site's content, data, and availability, and no vendor fix is currently available. Because the theme sits directly on the internet-facing surface of these sites, the exposure spans any customer-facing, marketing, or transactional property built on it, creating risk of data theft, defacement, malicious redirection, and downstream compromise of visitors. The practical likelihood is tempered by the fact that no public exploit code or confirmed active exploitation has been identified, and successful attacks depend on an additional gadget chain being present, so leadership should treat this as a high-priority remediation and inventory problem rather than an active incident.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the affected theme on internet-facing sites, replace it with a maintained alternative, deploy WAF rules or virtual patching that block crafted serialized input to theme endpoints, restrict or disable anonymous access to those endpoints at the web server or edge, and monitor affected sites for unauthorized file changes, new administrator accounts, and outbound connections until a vendor fix is available.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
Exploit-DB