CVE-2026-103039
Last modified
CVE-2026-103039 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 0.51% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Gravity Forms | Gravity Forms | <= 3.1.2 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-103039?
How severe is CVE-2026-103039?
How do I fix CVE-2026-103039?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-10302A flaw has been found in itsourcecode Fees Management System…6.3
- CVE-2026-103028SFTPGo is an open source, event-driven file transfer solutio…4.3
- CVE-2026-10303In ServerCo getssl version 2.49 and prior, the ACME challeng…7.4
- CVE-2026-103030Dio is a powerful HTTP client for Dart and Flutter. From 1.0…7.5
- CVE-2026-103036oRPC is a tool that helps build APIs that are end-to-end typ…6.5
- CVE-2026-103038PingTools Network Utilities 4.64 contains an OS command inje…8.6
- CVE-2026-103040LightLLM through 1.2.0 contains a remote code execution vuln…9.8
- CVE-2026-103041LightLLM through 1.2.0 multimodal deployments expose an unau…9.8
- CVE-2026-103042LightLLM through 1.2.0 contains a memory exhaustion vulnerab…7.5
- CVE-2026-103043anchorme through 3.0.8 contains a regular expression denial …7.5
- CVE-2026-103044XML injection (aka blind XPath injection) vulnerability in T…9.8
- CVE-2026-103045Improper neutralization of input during web page generation …6.1
Are you affected by CVE-2026-103039?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
