Check your own app — free, in about a minute.
The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.
Run the free mini-scan →A form builder that creates posts from submissions is a code path from a stranger's input straight into your data model. In Gravity Forms, one field type on that path hands the submitted value to PHP's maybe_unserialize() — which means a form submission can arrive as PHP objects. That is CVE-2026-103039, an unauthenticated PHP object injection scoring CVSS 9.8, and the CVE record names no patched version yet.
CVE-2026-103039 is a PHP object injection vulnerability in the Gravity Forms plugin for WordPress (vendor: Rocketgenius), disclosed October 30, 2026 (CNA: Wordfence).
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Network-reachable, low complexity, no privileges, no user interaction.GFFormsModel::create_post() passes the submitted value to WordPress's unrestricted global maybe_unserialize(). PHP object injection is a code-execution-class flaw when a usable gadget (POP) chain exists in the site's other installed code; whether a given site has such a chain is a property of that site, not something anyone can promise from the CVE alone.Exposure requires a form carrying a Post Custom Field of List type. A site whose forms use no such field is not exposed through this path — check your forms before you panic, and check them before you relax. The second half of the scope is the gadget chain: object injection becomes code execution when the site's other code (another plugin, a theme) provides a usable chain. Neither condition is visible from outside your site, which is exactly why the remediation below is field-by-field rather than a shrug.
Check wp-admin → Plugins for Gravity Forms and its version. At 3.1.2 or below, you are in the affected range. Then check your forms for Post Custom Fields with the List input type — those forms are the exposed surface.
One honesty note, because it is the whole point of how we cover these: our scanner does not claim a version check for this one. Gravity Forms is a premium plugin with no wordpress.org listing, and no primary source confirms a readable version disclosure a passive check could key on without guessing. Keying a check to a guessed install slug would produce claims we cannot stand behind in either direction. This article exists because the flaw is real and urgent — not because we can detect it passively. What the free mini-scan can do is check the rest of your site's exposed surface while you handle this one by hand.
Form builders that create posts from submissions are not collecting data — they are executing a write path into your site's data model with a stranger holding the pen. Every field type on such a form is attack surface, and the dangerous ones are the ones that treat submitted values as structured data: the moment a field value is unserialized, evaluated, or merged into settings, it stops being a submission and becomes instructions. When an AI builder wires a form to post creation, the review question is never "does it save?" It is "what is the most structured thing this field will accept — and who gets to send it?"
Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the audit finds a stranger.
Running WordPress with Gravity Forms? Check your version and your List-type post fields today, then run the free check at preshipit.com/free-scan — it covers the exposures a scan can see, and articles like this one cover the ones it can't.
The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.
New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.
Check your own app — free, in about a minute.
The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.
Run the free mini-scan →← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report