Critical PHP object injection in Gravity Forms (CVE-2026-103039)
Gravity Forms versions up to and including 3.1.2 contain an unauthenticated PHP object injection flaw (CVE-2026-103039, CVSS 9.8). The flaw sits in a Post Custom Field with a List input type and a content template enabled: the plugin passes the submitted value to WordPress’s unrestricted maybe_unserialize() function instead of its hardened equivalent, which allows an unauthenticated attacker to inject a PHP object into post meta.
Remote code execution from this flaw is conditional. Gravity Forms itself contains no gadget chain, so an attacker needs a chain from another plugin or theme, or a field mapped to the protected _wp_page_template meta key, which WordPress itself can turn into a chain on hosts with a readable PEAR install and register_argc_argv enabled. Forms that create posts through Post Custom Fields should still be treated as high priority, because the entry point needs no account.
Wordfence published the flaw on October 29, 2026, and credited researchers Tin Pham, Hao Ngo, and Trong Pham. No public exploit code had been confirmed as of October 30, 2026, but the flaw needs no account and the fix is a single update, so waiting for exploit reports would leave the window open.
What to do
- Update Gravity Forms to 3.1.3 or later immediately.
- After updating, review recently created posts and post meta for unexpected content, and check for unfamiliar admin users or files.
- If an update cannot be applied right away, take forms that create posts through Post Custom Fields offline until the update is applied.
A form plugin that creates posts is easy to leave out of an update routine. ZeroBreach’s recurring scans inventory every plugin on every app it watches and flag vulnerable versions before an attacker finds them.