WordPress Santé theme <= 1.5.1 - PHP Object Injection vulnerability
Description
Unauthenticated PHP Object Injection in WordPress Santé theme <= 1.5.1 allows remote code execution via deserialization of untrusted input.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Unauthenticated PHP Object Injection in WordPress Santé theme <= 1.5.1 allows remote code execution via deserialization of untrusted input.
Vulnerability
The WordPress Santé theme versions 1.5.1 and earlier contain an unauthenticated PHP Object Injection vulnerability [1]. The flaw exists due to unsafe deserialization of user-supplied input without proper sanitization or validation, enabling an attacker to inject arbitrary PHP objects. Affected versions are all releases up to and including 1.5.1.
Exploitation
An attacker can exploit this vulnerability remotely without authentication by sending a crafted request containing a malicious serialized PHP object [1]. No special network position or user interaction is required; the vulnerability is reachable through standard HTTP requests to the theme's processing functions.
Impact
Successful exploitation can lead to arbitrary code execution, SQL injection, path traversal, denial of service, and other severe consequences if a suitable POP (Property-Oriented Programming) chain is available [1]. The attacker gains full control over the affected WordPress site, potentially compromising data, integrity, and availability.
Mitigation
The vulnerability is fixed in version 1.6 of the Santé theme [1]. Users are strongly advised to update immediately. If updating is not possible, Patchstack provides a mitigation rule to block attacks until the update can be applied [1]. The vulnerability is considered high risk and is expected to be actively exploited in mass campaigns [1].
AI Insight generated on Jun 17, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
1- WordPress: 25 CVEs Disclosed in One Day — RCE, File Upload, and a Wave of PHP Object Injection Flaws in ThemesVypr Intelligence · Jun 16, 2026