Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach vulnerable theme endpoint
-
DeliverySubmit crafted serialized object
-
ExploitTrigger unserialize object injection
-
ExecutionInvoke POP gadget chain
-
ImpactCode execution or data compromise
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 vulnerability is PHP object injection via deserialization of untrusted data in the ThemeREX Save Life theme (versions up to and including 1.2.14). The supplied CVSS vector is PR:N/UI:N, so no authentication or user interaction is indicated, but the specific feature, parameter, or endpoint that passes attacker data to unserialize() is not described in the available sources. A practical limiting factor for CWE-502 object injection is that meaningful impact (code execution, file or database operations) generally requires a reachable POP gadget chain in the theme, an installed plugin, or WordPress core; the evidence does not confirm such a chain exists, so real-world impact may be narrower than the 9.8 score implies. Exploitation is also limited to sites running the Save Life theme at version 1.2.14 or earlier. |
| Impact | The input presents a strong but partly unverified risk picture. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) describes a remotely reachable, low-complexity, unauthenticated flaw with full confidentiality, integrity and availability impact, and the vuln.today priority is labelled act_now. However, several signals that would normally corroborate that urgency are absent: no EPSS probability is provided, the CVE is not listed in CISA KEV, and no SSVC decision tree (automatable/technical-impact) is supplied - the act_now label is the only decision signal and it comes from an aggregator, not CISA. CWE-502 (deserialization of untrusted data / PHP object injection) is genuinely dangerous, but its real-world impact depends on the presence of a usable POP gadget chain in the theme or the loaded plugin/WordPress stack, and the description does not state how the untrusted data reaches unserialize() or whether a gadget chain is reachable - so the C:H/I:H/A:H rating is a worst-case assumption, not a demonstrated outcome. The only reference is a Patchstack database entry; it is a vulnerability record, not verified working exploit code. Net assessment: treat as a high-priority patch candidate given the network-unauthenticated CVSS and act_now label, but note that exploitability hinges on an undisclosed gadget chain and that no EPSS/KEV/exploit evidence confirms active or widespread exploitation - this looks like a Patchstack-researcher finding rather than a mass-exploited threat. |
| Exploit ScenarioDerived | A remote attacker submits a crafted serialized PHP payload to an input that the Save Life theme passes to unserialize(), instantiating attacker-chosen objects (PHP object injection). If a suitable POP gadget chain exists in the theme, loaded plugins, or WordPress core, this could escalate to file operations, SQL interaction, or code execution. No verified working exploit code is identified; only a Patchstack vulnerability reference exists, and the exact trigger is not described in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 23, 2026
PHP object injection in the ThemeREX Save Life WordPress theme through version 1.2.14 lets remote attackers route crafted serialized data into an unsafe unserialize() path, scored 9.8 under CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H with high confidentiality, integrity and availability impact. The specific feature, parameter or endpoint that reaches the deserialization sink is not described in the available sources, and a usable POP gadget chain in the theme, an installed plugin or WordPress core is unconfirmed, so realized impact may be narrower than the score implies. No CISA KEV entry or public exploit code is associated with this CVE in the supplied intelligence, although the vuln.today decision label is act_now.
RemediationAI
No vendor-released patch is identified in the available data - no fixed version is listed, and the only reference is the Patchstack vulnerability database entry (https://patchstack.com/database/wordpress/theme/save-life/vulnerability/wordpress-save-life-theme-1-2-14-php-object-injection-vulnerability?_s_id=cve), which should be monitored for a corrected release. Because exposure is confined to sites running Save Life at version 1.2.14 or earlier, deactivating and deleting the theme removes the vulnerable code entirely (side effect: loss of the theme's layout, templates and any customizations built on it), and switching to a maintained theme achieves the same removal while keeping the site's design. If the theme must remain installed, limiting which users and request paths can reach theme-exposed input handling reduces the attack surface, at the cost of restricting legitimate theme functionality, and this is only a stopgap until a patched version appears in the advisory.
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 root cause class is CWE-502, deserialization of untrusted data, in a PHP-based WordPress theme. PHP unserialize() applied to attacker-controlled input allows arbitrary class instantiation, which becomes exploitable for file operations, database access or code execution only when a reachable POP (property-oriented programming) gadget chain exists in the theme itself, a co-installed plugin or WordPress core. The CPE cpe:2.3:a:themerex_group:save_life:*:*:*:*:*:*:*:* identifies the affected package as ThemeREX Group's Save Life theme, with the vendor advisory scoped to releases through 1.2.14. The supplied vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H indicates a network-reachable, unauthenticated, no-interaction path with unchanged scope and high impact across all three properties, but the sources do not state which theme feature, request parameter or AJAX/REST endpoint feeds the unserialize() sink, nor do they confirm that a functional gadget chain is present; both of those determine whether the 9.8 severity translates into code execution or a more limited object-injection primitive.
Know when Save Life 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
No authentication or user interaction is stated (PR:N/UI:N) and the theme is network-reachable (AV:N); C/I/A kept High as the worst-case object-injection outcome, though the trigger is not described.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Deserialization of Untrusted Data vulnerability in ThemeREX Group Save Life save-life allows Object Injection.This issue affects Save Life: from n/a through 1.2.14.
Articles & Coverage 1
Executive ViewAI
A critical unauthenticated PHP object injection flaw exists in the ThemeREX Save Life WordPress theme (through version 1.2.14) that could allow remote attackers to compromise confidentiality, integrity, and availability of affected sites. Any organization hosting this theme on internet-facing WordPress installations should treat the exposure as a priority, since successful exploitation could expose customer data, allow content or configuration tampering, and disrupt site availability.
No vendor-released patch identified at time of analysis. Interim mitigations: disable or remove the ThemeREX Save Life theme where feasible, deploy WAF rules to block serialized payload patterns targeting theme endpoints, restrict direct access to theme files, and monitor web logs for indicators of deserialization attempts.
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.
EUVD-2026-108951
GHSA-3cwm-hcqf-g7j5
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB