A critical Gravity Forms flaw, CVE-2026-103039, rated 9.8 out of 10 (CVSS 3.1), was disclosed on 29 Oct. It needs no login: a visitor submitting a form can plant data that, on some setups, leads to a full takeover of the site. The fix has been available since 1 Oct, in version 3.1.3. The catch is how it shipped: the changelog said "Added security enhancements", a line that appears in almost every release.
In short: CVE-2026-103039 is a critical Gravity Forms flaw, rated 9.8, in every version up to 3.1.2. Forms that create WordPress posts with a Post Custom Field set to the List input can let a visitor with no account inject a PHP object, which on some setups can lead to remote code execution. Update to 3.1.3 or later.
What the flaw is, in plain English
Gravity Forms can turn a form submission into a WordPress post, for example a user-submitted listing, directory entry or testimonial. One of the fields that does this, the Post Custom Field, can use a List input. In versions up to 3.1.2, the value sent through that field is unpacked by a function that will rebuild PHP objects from whatever the visitor sends, instead of the safer version Gravity Forms added in 3.1.1.
On its own, that lets an attacker plant a PHP object in the new post's data. What happens next depends on the rest of your site. Gravity Forms itself contains no code an attacker can chain this to, but another plugin or theme might, and that can lead to remote code execution. The advisory also describes a route through WordPress's own code when the field is mapped to the page template setting, which leads to remote code execution on servers with a readable PEAR install and register_argc_argv enabled.
Who is exposed
You are likely exposed if all of these are true:
A plain contact form with name, email and message fields doesn't use Post fields, so this particular flaw doesn't reach it. Don't stop there, though. Two other Gravity Forms flaws were disclosed the same day, both rated 7.2: stored cross-site scripting through the List field, and through Post Excerpt, Post Custom Field and rich-text Paragraph values. Updating to the current release closes all three.
Has it been exploited?
We haven't seen reports of attacks using this flaw yet, and it isn't on the public catalogue of known exploited vulnerabilities. It is rated as likely to be exploited, though. Flaws that need no login are often picked up by automated attacks that scan thousands of sites at once, whatever their size.
Why so many sites missed the fix
That third point is the same lesson as the Laravel authentication flaw and PHP2Shell: when the fix only exists in a newer major version, the fix is an upgrade, not a patch.
What to do this week
The same day: a WordPress AI plugin flaw
Also disclosed on 29 Oct: CVE-2026-110732, rated 7.5, in a popular WordPress AI chatbot plugin that lets AI assistants connect to and manage your site. Up to version 3.8.6, anyone could register an app connection without logging in. If an administrator then approved that app on the sign-in screen, which an attacker could disguise, the attacker got admin-level control of the site. It only applies with the plugin's AI connection feature switched on, and it was fixed in version 3.8.7 on 23 Oct.
The wider point: every AI plugin bolted onto an older WordPress site adds new ways in, and they need the same update routine as everything else. Our checklist for production AI integrations covers the basics.
A basic update and monitoring routine
This is what we'd set up for any business site that takes submissions (our view):
If your site is old enough that updates feel risky, that's usually a sign the upgrade path needs planning, not avoiding. Our piece on the real cost of technical debt explains why.
FAQ
Is every site running Gravity Forms vulnerable?
No. This flaw needs version 3.1.2 or older and a form that uses a Post Custom Field set to the List input. Two other flaws disclosed the same day are wider, so update anyway.
Which version fixes it?
3.1.3, released on 1 Oct 2026. The current release is 3.2.1. Update to 3.1.3 or later.
I'm on Gravity Forms 2.x. Is there a patch?
No 2.x version fixes it. You need to upgrade to 3.x, which doesn't happen automatically and can break customisations, so test it on a staging copy first.
Has it been exploited?
We haven't seen reports of attacks using it yet. It is rated as likely to be exploited, and flaws that need no login are often used in automated attacks.
My auto-updates are on. Am I safe?
On 3.x, probably, but check the version number. Updates can roll out gradually, and major versions never update themselves.
Can I switch something off instead?
Removing or unpublishing forms that use Post fields reduces the risk while you update, but updating is the fix.
Need a hand?
Not sure what version you're on, or worried a 2.x to 3.x upgrade will break your forms? Book a free consult and we'll check what you're running and plan the update. We can run your updates and monitoring as your tech team, or work alongside your developers as a senior team. See our services or message us on WhatsApp +971 585692165.
Sources: NVD record for CVE-2026-103039, Gravity Forms changelog, Gravity Forms version numbering, Checks before upgrading to Gravity Forms 3.0. Checked on 30 Oct 2026.