CVE-2026-103039

Gravity Forms <= 3.1.2 - Unauthenticated PHP Object Injection via Post Custom Field

Published Oct 30, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gravity Forms to a newer release (any version greater than 3.1.2) where the unserialize function uses GFCommon::maybe_unserialize() with object instantiation disabled.
  • If an upgrade is not immediately possible, remove all List‑type custom fields from forms, particularly those configured with content templates or mapped to the _wp_page_template meta key.
  • Configure WordPress to disable register_argc_argv and ensure no readable PEAR installation is present, which mitigates the template‑based remote code execution path.

Generated by OpenCVE AI on October 30, 2026 at 08:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gravityforms
Gravityforms gravity Forms
Wordpress-extensions
Wordpress-extensions gravity Forms
Vendors & Products Gravityforms
Gravityforms gravity Forms
Wordpress-extensions
Wordpress-extensions gravity Forms
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Gravity Forms <= 3.1.2 - Unauthenticated PHP Object Injection via Post Custom Field
Weaknesses CWE-502
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
Oct 30, 2026, 3:57 PM
Reserved
Sep 29, 2026, 10:08 PM
Status
Deferred
Published
Oct 30, 2026, 7:16 AM
Modified
Oct 30, 2026, 4:17 PM