CVE-2026-49105
Description
Unauthenticated PHP Object Injection in WP Zendesk plugin for WordPress <= 1.1.4, leading to code injection or SQL injection if a POP chain is present.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Unauthenticated PHP Object Injection in WP Zendesk plugin for WordPress <= 1.1.4, leading to code injection or SQL injection if a POP chain is present.
Vulnerability
The WP Zendesk for Contact Form 7, WPForms, Elementor, Formidable and Ninja Forms plugin for WordPress is vulnerable to unauthenticated PHP Object Injection in versions 1.1.4 and earlier. The flaw exists in the plugin's handling of serialized input without proper sanitization or validation, allowing an attacker to inject arbitrary PHP objects if a suitable gadget chain is available in the application or its extensions [1].
Exploitation
An attacker can exploit this vulnerability remotely without requiring any authentication. The attacker sends a crafted HTTP request containing malicious serialized data to the vulnerable plugin endpoint. No user interaction is required, and the attacker does not need any prior access or privileges on the WordPress site [1].
Impact
Successful exploitation can lead to arbitrary code execution, SQL injection, path traversal, denial of service, or other severe outcomes, depending on the presence and availability of a proper Property-Oriented Programming (POP) chain in the WordPress environment [1]. This could result in complete compromise of the affected site.
Mitigation
The vulnerability has been fixed in version 1.1.5 of the plugin. Users are strongly advised to update to version 1.1.5 or later immediately. Patchstack has released a mitigation rule to block attacks for users who cannot update immediately [1]. This vulnerability is expected to be widely exploited and is listed as critical.
AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2- Range: <=1.1.4
Patches
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- Wordfence Intelligence Weekly WordPress Vulnerability Report (June 1, 2026 to June 7, 2026)Wordfence Blog · Jun 11, 2026