Live › vulnerability › CVE-2026-103039
Gravity Forms up to and including 3.1.2 passes a submitted post custom field value to WordPress's unrestricted maybe_unserialize(), letting an unauthenticated attacker inject a PHP object into post meta. The plugin has no gadget chain of its own, but a gadget in another plugin or theme, or WordPress core via the _wp_page_template meta key on hosts with a readable PEAR install and register_argc_argv enabled, could allow remote code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 07:29 UTC. All times on this page are UTC.
Sites running the Gravity Forms WordPress plugin version 3.1.2 or earlier that use the Post Custom Field of input type List with a content template enabled. Exposure to code execution depends on a gadget chain in another plugin or theme, or on WordPress core via the _wp_page_template key with PEAR installed and register_argc_argv enabled; sites without these can still face data manipulation through injected post meta, and sites on a later plugin version are not affected.
No product ranges from the sources yet.
3.1.2 or earlier is affected per the description)3.1.2 (the fixed version is not stated in the sources)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Gravity Forms plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.1.2 via a Post Custom Field whose input type is List. This is due to GFFormsModel::create_post() passing the submitted value to WordPress' unrestricted global maybe_unserialize() rather than the plugin's own hardened GFCommon::maybe_unserialize(), which was added in 3.1.1 and passes allowed_classes => false precisely to prevent object instantiation. Where the field has a content template enabled, the submitted row reaches that call verbatim. This makes it possible for unauthenticated attackers to inject a PHP object into post meta. No PHP Object Injection gadget chain is present in the plugin itself; however, if a gadget chain is present via an additional plugin or theme, it could allow the attacker to perform actions such as remote code execution. Where the custom field is mapped to the protected _wp_page_template meta key, WordPress itself supplies the chain: validate_file() accepts non-scalars, WP_Theme::__toString() then resolves an attacker-controlled path, and on hosts with a readable PEAR install and register_argc_argv enabled this yields remote code execution.
This page as .md · .json · in your agent: get_signal("CVE-2026-103039")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.