Home › Vulnerabilities

Gravity Forms Flaw CVE-2026-103039: Update Now

Published October 30, 2026 · Last updated October 30, 2026

CVE Critical Patch

The short version: CVE-2026-103039 is a critical-severity security flaw in Gravity Forms. The National Vulnerability Database (NVD) published it on October 30, 2026, and the score it lists is 9.8 out of 10. When FraudMeNot checked on October 30, 2026, CISA had not added CVE-2026-103039 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-103039

The record was filed by wordfence.com. In its own words: "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."

Why Gravity Forms admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on wordfence.com rated CVE-2026-103039 9.8 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Gravity Forms running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Affected Gravity Forms releases

According to the record, these releases are vulnerable:

  • 0 through 3.1.2

The type of bug behind CVE-2026-103039

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-502, Deserialization of Untrusted Data. MITRE describes this class of bug as follows: "The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid."

Vendor remediation for CVE-2026-103039

The vendor advisory remediation for operators of Gravity Forms, quoted for this page, is: "Update the Gravity Forms plugin to a release newer than 3.1.2 (the latest version from your Gravity Forms account or the WordPress dashboard). Until you can update, disable any form that uses a Post Custom Field of the List input type with a content template, and check post meta for unexpected serialized objects. WordPress site owners, agencies, and hosting providers running Gravity Forms should act now."

What to do about it

  • Update now: Update the Gravity Forms plugin to a release newer than 3.1.2 (the latest version from your Gravity Forms account or the WordPress dashboard). Until you can update, disable any form that uses a Post Custom Field of the List input type with a content template, and check post meta for unexpected serialized objects. WordPress site owners, agencies, and hosting providers running Gravity Forms should act now.
  • Who should act: IT teams, managed service providers, and developers who run or ship Gravity Forms. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Gravity Forms (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from October 30, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-103039. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-103039 record details from CISA and NVD

  • Attack complexity for CVE-2026-103039: low
  • CVE-2026-103039 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-103039: exploitability 3.9, impact 5.9.
  • Who mapped the weakness type: the address listed on wordfence.com (Primary)
  • References in the NVD record: 2.

Dates to know

  • October 30, 2026: NVD publishes CVE-2026-103039.
  • October 30, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-103039 is not listed.
  • October 30, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.