EUVD-2026-96460
GHSA-7pq8-46v4-4wp9
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Subscriber account on target site
-
DeliveryCraft malicious serialized PHP object
-
ExploitSubmit payload to vulnerable endpoint
-
ExecutionTrigger unsafe deserialization (POP chain)
-
ImpactAchieve code execution or file 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 | Requires an authenticated WordPress account at Subscriber level (the lowest role, often available via open user registration) on a site running the Angio theme version 1.1.1 or earlier. The attacker must be able to reach the vulnerable endpoint over the network and supply attacker-controlled serialized data that the theme deserializes unsafely. Meaningful impact (code execution, file manipulation) further depends on the presence of a usable PHP object-injection gadget chain in the theme, active plugins, or WordPress core; without such a chain, practical impact is reduced. Limiting factors: authentication is mandatory (no anonymous exploitation), and the Angio theme must be installed and active. |
| Impact | This is a genuine priority-worthy flaw but not an emergency. The provided CVSS vector (AV:N/AC:L/PR:L/UI:N) describes network-reachable, low-complexity exploitation requiring only low-privileged authentication - PR:L maps to a WordPress Subscriber account, which is the lowest tier and often self-registerable, so the authentication barrier is weak on sites permitting open registration. CWE-502 (deserialization) with C:H/I:H/A:H indicates full compromise of the vulnerable component is plausible if a usable POP gadget chain exists. However, several escalating signals are absent: no CISA KEV listing, no EPSS score was supplied, and no public proof-of-concept is referenced - so there is no public exploit identified at time of analysis and no evidence of active exploitation. A critical caveat: PHP Object Injection impact is contingent on a reachable gadget chain in the theme, installed plugins, or WordPress core; CVSS encodes the worst-case (H/H/H) outcome, but real-world impact may be lower if no exploitable chain is present. Net: credible, remotely reachable, low-barrier bug meriting prompt patching, but currently theoretical rather than demonstrated in the wild. |
| Exploit ScenarioDerived | An attacker registers or obtains a Subscriber-level account on a WordPress site running the Angio theme (<= 1.1.1), then sends a crafted request containing a malicious serialized PHP object to the vulnerable endpoint. If a suitable POP gadget chain is available in the theme, plugins, or core, deserialization triggers it to achieve outcomes such as arbitrary file operations or code execution. No public exploit code is identified at time of analysis, and exploitation requires authentication. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
PHP object injection in the Angio WordPress theme (versions 1.1.1 and earlier) allows authenticated attackers with Subscriber-level access to supply malicious serialized data, potentially achieving remote code execution, file manipulation, or other high-impact outcomes if a usable gadget chain exists in the theme, plugins, or WordPress core. Exploitation requires an authenticated Subscriber account (CVSS vector PR:L), which is often obtainable through open user registration, and no public exploit code or active exploitation has been identified at time of analysis. This is a priority-worthy flaw but not an emergency, as practical impact is contingent on the presence of a gadget chain.
RemediationAI
No vendor patch version is specified in the provided intelligence. Check the Patchstack advisory for a fixed release; if a patched version of the Angio theme is available, update immediately. If no patch exists, consider disabling or removing the Angio theme, as it is the vulnerable component-this may impact site appearance and functionality. Because exploitation requires an authenticated Subscriber-level account (the lowest role, often enabled via open user registration), restrict user registration and ensure Subscriber accounts are only granted to trusted users; this may reduce legitimate user onboarding. To limit the availability of a gadget chain, minimize the number of active plugins and keep WordPress core and all plugins updated. A web application firewall (WAF) can be configured to block serialized payloads directed at the theme's endpoints, but this is a mitigating control, not a fix, and may cause false positives. Monitor logs for suspicious requests containing serialized data from Subscriber accounts.
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 Angio theme for WordPress, developed by Rascals, fails to safely handle serialized user input, leading to a PHP object injection vulnerability classified as CWE-502 (Deserialization of Untrusted Data). When user-supplied data is passed to PHP's unserialize() function, an attacker can inject arbitrary PHP objects. If a suitable gadget chain exists-a sequence of classes with magic methods such as __destruct, __wakeup, or __toString that can be chained to perform dangerous operations-this can lead to remote code execution, file deletion, or other severe impacts. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates a network-exploitable flaw requiring low privileges (authenticated Subscriber) with no user interaction and high impact on confidentiality, integrity, and availability. The CPE cpe:2.3:a:rascals:angio:*:*:*:*:*:*:*:* confirms the affected product is the Angio theme; the vulnerability affects versions up to and including 1.1.1. Authentication is mandatory; anonymous exploitation is not possible per the assessed vector.
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:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable endpoint (AV:N), low complexity (AC:L), requires a Subscriber account so PR:L, no user interaction; object injection can yield full component compromise, hence C:H/I:H/A:H.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber PHP Object Injection in Angio <= 1.1.1 versions.
Executive ViewAI
Websites running the Angio WordPress theme at version 1.1.1 or earlier carry a high-severity PHP object injection flaw that could let someone with only a basic Subscriber account - access frequently granted through open user registration - manipulate files or execute code on the hosting server. The immediate business concern is that every site using this theme is unpatched and must be managed through interim controls. No public exploit identified at time of analysis, and practical impact hinges on whether a usable gadget chain exists in the theme, its plugins, or WordPress core, so the risk is real but conditional.
No vendor-released patch identified at time of analysis; interim mitigations include removing or replacing the Angio theme (1.1.1 and earlier), disabling open user registration and limiting or auditing Subscriber-level accounts, deploying WAF or virtual-patch rules that block object-injection and serialized payloads, hardening WordPress core and plugin inventory to eliminate usable gadget chains, and monitoring the web root for unauthorized file changes.
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