Grand Wedding < 3.1.11 - Unauthenticated PHP Object Injection
Strategic Overview
- Status
- Patched in 3.1.11
- Affected Theme
- Grand Wedding WordPress
- Affected Version
< 3.1.11- CVSS
- 8.1High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2026-22417
At a glance
CVE-2026-22417 is a high-severity Deserialization of Untrusted Data vulnerability in the Grand Wedding WordPress WordPress theme, affecting versions < 3.1.11. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.1.11; sites on affected versions should update now. Disclosed March 2026, reported by Tran Nguyen Bao Khanh.
Vulnerability Overview
The Grand Wedding theme for WordPress is vulnerable to PHP Object Injection in versions up to, and excluding, 3.1.11 via deserialization of untrusted input. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
Reaching this weakness in Grand Wedding WordPress < 3.1.11 takes no account at all. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Grand Wedding WordPress the fix is 3.1.11: builds < 3.1.11 are affected, anything from 3.1.11 onward is not.
Remediation
Update to version 3.1.11, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Grand Wedding WordPress 3.1.11 closes this, and updating the theme is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C