PT-2026-133295

CVE-2026-103039

·

Published

2026-10-29

·

Updated

2026-11-08

Description by

CVSS 3.1
9.8
Critical
MetricsAV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Name of the Vulnerable Software and Affected Versions Gravity Forms versions prior to 3.1.3
Description An unauthenticated attacker can perform PHP Object Injection via a Post Custom Field with a List input type. The issue occurs because the GFFormsModel::create post() function passes submitted values to the unrestricted global maybe unserialize() function instead of the hardened GFCommon::maybe unserialize() function, which prevents object instantiation by setting allowed classes to false. When a content template is enabled for the field, the submitted row is processed verbatim, allowing the injection of a PHP object into post meta. While the plugin lacks its own gadget chain, the presence of one in another plugin or theme could lead to remote code execution. Specifically, if the custom field is mapped to the wp page template meta key, the validate file() function and WP Theme:: toString() can be leveraged to achieve remote code execution on hosts with a readable PEAR install and register argc argv enabled.
Recommendations Update Gravity Forms to a version newer than 3.1.2.
Exploitability
Fix
Impacts
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾