Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-103039— Gravity Forms <= 3.1.2 - Unauthenticated PHP Object Injection via Post Custom Field

Quick assessment

Affected
Gravity Forms Gravity Forms
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

WordPress 的 Gravity Forms 插件在所有 3.1.2 及更早版本中存在 PHP 对象注入漏洞。该漏洞源于：当自定义字段（Post Custom Field）的输入类型为“列表（List）”时，GFFormsModel::create_post() 方法将用户提交的数据直接传递给 WordPress 全局的、未加限制的 maybe_unserialize() 函数，而非插件自身在 3.1.1 版本中引入的加固版本 GFCommon::maybe_unserialize()。后者通过设置 allo

CVSS 9.8 · Critical
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-103039

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Gravity Forms <= 3.1.2 - Unauthenticated PHP Object Injection via Post Custom Field
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
可信数据的反序列化
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Gravity Forms Gravity Forms 0 ~ 3.1.2 -

II. Public POCs for CVE-2026-103039

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-103039

请登录查看更多情报信息。

Other References for CVE-2026-103039 (2)

Same Patch Batch · Gravity Forms · 2026-10-30 · 3 CVEs total

CVE-2026-90437 7.2 HIGH Gravity Forms <= 3.1.1 - Unauthenticated Stored Cross-Site Scripting via Post Excerpt / Po
CVE-2026-97645 7.2 HIGH Gravity Forms <= 3.1.2 - Unauthenticated Stored Cross-Site Scripting via List Field

IV. Related Vulnerabilities

Same product: Gravity Forms
Same vendor: Gravity Forms
Same weakness: CWE-502