Technical impact
Gravity Forms, a popular WordPress plugin, is vulnerable to PHP Object Injection in all versions up to 3.1.2 through a Post Custom Field of type List. The plugin incorrectly forwards user‑submitted values to WordPress' global maybe_unserialize() instead of its own hardened GFCommon::maybe_unserialize(), which disallows object instantiation. By submitting crafted data in such a field, an unauthenticated attacker can place a PHP object directly in post meta. While the plugin itself does not contain a gadget chain, the presence of vulnerability in conjunction with a gadget chain from another plugin or theme can lead to arbitrary code execution. Additionally, if the custom field is mapped to the protected _wp_page_template meta key, WordPress’ validate_file() and WP_Theme::__toString() can resolve an attacker‑controlled path, and on systems with a readable PEAR installation and register_argc_argv enabled this can also result in remote code execution.
Affected Systems
All installations of Gravity Forms for WordPress with version 3.1.2 or earlier are affected. No specific WordPress core or theme versions are listed as affected; however, the risk exists on any host running an affected Gravity Forms plugin.
Risk and Exploitability
The vulnerability receives a CVSS score of 9.8, indicating critical severity. The EPSS score is currently unavailable, and it is not listed in CISA’s KEV catalog. The attack vector is unauthenticated and exploits universal user input in a List‑type custom field, making it trivially exploitable on any WordPress site with the vulnerable plugin installed. The potential impact ranges from data integrity compromise via logged object data to full remote code execution if a gadget chain is present or if WordPress’ own template handling can be abused as described.