Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Orpheus theme ≤1.8
-
DeliverySend crafted unauthenticated HTTP request
-
ExploitDeliver malicious serialized PHP object
-
ExecutionTrigger unsafe deserialization (CWE-502)
-
PersistChain available POP gadget
-
ImpactCompromise confidentiality, integrity and 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 | The affected component is the ThemeRex Orpheus WordPress theme at version 1.8 or earlier, which must be installed and active on the target site. Per the CVSS vector (PR:N/UI:N) exploitation is unauthenticated and requires no user interaction, so no special configuration or privilege is stated as a precondition. The exact injection point (parameter, endpoint, or feature) that reaches the unsafe deserialization is not described in the available sources, and the trigger mechanism is not detailed. The primary limiting factor is that practical object-injection impact depends on a usable PHP gadget (POP) chain being present in the theme, WordPress core, or co-installed plugins - a condition the sources do not confirm - and that only sites running Orpheus ≤1.8 are exposed. |
| Impact | Signals point in two directions and must be weighed together. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H, base 9.8) describes a maximally severe case: network-reachable, low-complexity, no privileges and no user interaction, with full confidentiality, integrity and availability loss - consistent with CWE-502 PHP Object Injection that can escalate to code execution. The vuln.today decision label is act_now, and the issue was reported by Patchstack, a credible WordPress vulnerability source. Against that, there is NO EPSS score, NO CISA KEV listing, and NO public exploit or PoC reference in the supplied data (the only reference is the Patchstack database entry, not exploit code), so there is no public exploit identified at time of analysis. The act_now priority therefore appears driven by severity and the unauthenticated nature of the flaw rather than by observed exploitation - treat it as high-priority to patch, but note that real-world exploitability of PHP Object Injection depends on a usable gadget (POP) chain being reachable, which the available sources do not confirm. Net: a genuine high-priority patching item on the merits of an unauthenticated, network-facing deserialization flaw, but with no evidence of active or automated exploitation to date; prioritize based on severity and exposure, not on confirmed in-the-wild activity. |
| Exploit ScenarioDerived | A remote attacker sends a crafted request to a WordPress site running the Orpheus theme (version 1.8 or earlier) containing a malicious serialized PHP object, which the theme deserializes without authentication (AV:N/AC:L/PR:N/UI:N). If a suitable gadget chain is present in the theme, WordPress core, or another installed plugin, the object injection can be escalated toward data manipulation or code execution. No public exploit or PoC code is identified in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
Unauthenticated PHP object injection in the ThemeRex Orpheus WordPress theme, affecting versions 1.8 and earlier, lets remote attackers reach unsafe deserialization of attacker-supplied data, carrying an assessed CVSS of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) against confidentiality, integrity and availability. The exact injection point, endpoint or feature that reaches the unsafe unserialize call is not described in the available sources, and real-world impact depends on a usable PHP gadget (POP) chain existing in the theme, WordPress core, or co-installed plugins, which the sources do not confirm. No public exploit code or CISA KEV entry was identified at time of analysis, but the issue is prioritized act_now in vuln.today's decision signals and was reported through Patchstack.
RemediationAI
No vendor-released patch is identified in the supplied data, and the provided reference (https://patchstack.com/database/wordpress/theme/orpheus/vulnerability/wordpress-orpheus-theme-1-8-php-object-injection-vulnerability?_s_id=cve) is the authoritative place to check for a fixed Orpheus release before acting. Because the vulnerability is unauthenticated and needs no user interaction, the exposure is present for any site with Orpheus 1.8 or earlier active, so the direct compensating control traceable to this data is to stop running the affected theme version on exposed sites - deactivate or remove Orpheus ≤1.8 until a patched build is confirmed - accepting the trade-off that the site loses the theme's layout and presentation. Note that removing the theme does not retroactively undo any compromise, and that the effectiveness of any partial measure depends on the unidentified injection point, so verifying a fix against the vendor advisory takes precedence over interim workarounds.
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 CWE-502 (Deserialization of Untrusted Data) in a PHP-based WordPress theme distributed by ThemeRex. PHP object injection occurs when attacker-controlled serialized input is handed to unserialize(), which reconstructs arbitrary objects and runs their magic methods (__wakeup, __destruct, __toString and similar); if any class reachable in the loaded codebase has exploitable magic-method behaviour, this can escalate from object injection to file operations, SQL execution or code execution. The CPE cpe:2.3:a:themerex:orpheus:*:*:*:*:*:*:*:* confirms the affected component is the Orpheus theme itself rather than WordPress core, with the vulnerable range ending at 1.8 per the reported description. The CVSS vector places the attack over the network at low complexity with no privileges (PR:N) and no user interaction (UI:N), and scope is assessed as unchanged (S:U), meaning the impact is scored against the theme's own security authority even though the practical gadget chain may be supplied by other installed code. The available sources do not state which request path, parameter or theme feature performs the unsafe deserialization, nor which classes could form a working chain, so the precise trigger mechanism remains unverified.
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
Unauthenticated network-reachable deserialization with no user interaction yields AV:N/AC:L/PR:N/UI:N; object injection escalating toward code execution supports C:H/I:H/A:H, scope unchanged.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated PHP Object Injection in Orpheus <= 1.8 versions.
Executive ViewAI
A critical vulnerability in the ThemeRex Orpheus WordPress theme (versions 1.8 and earlier) allows unauthenticated attackers to inject malicious PHP objects, potentially leading to full site compromise. This affects any organization using this theme on public-facing WordPress sites, risking data theft, defacement, or service disruption. Leadership should prioritize immediate remediation to protect brand reputation and customer trust.
Apply vendor patch.
Threat Intelligence Overview
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
EUVD-2026-112971
GHSA-3r4p-5j69-675v
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB