Is there a public exploit for CVE-2026-103039?

Yes. Proof-of-concept code for CVE-2026-103039 has been published publicly.

Is there a proof of concept for CVE-2026-103039?

Yes — 1 proof-of-concept entry is linked on this page, from public repositories and community submissions. They are listed for authorised testing only.

How severe is CVE-2026-103039?

CVE-2026-103039 scores CVSS 9.8 (v3.1), rated critical.

9.8 Critical

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…

CVE-2026-103039

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::createpost() passing the submitted value to WordPress' unrestricted global maybeunserialize() rather than the plugin's own hardened GFCommon::maybeunserialize(), which was added in 3.1.1 and passes allowedclasses => 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 wppagetemplate meta key, WordPress itself supplies the chain: validatefile() accepts non-scalars, WPTheme::toString() then resolves an attacker-controlled path, and on hosts with a readable PEAR install and registerargcargv enabled this yields remote code execution.

Proof-of-concept code is published

Public PoC

Public PoCnoxcrypt-x/CVE-2026-1030392 stars

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Assessment

CVSS: 9.8 (v3.1)
Severity: Critical
Known exploited: Not listed in CISA KEV
Exploit availability: Public PoC
Published: 30 October 2026
Last updated: 30 October 2026
Weakness: CWE-502
Assigner: security@wordfence.com

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 4 + 3? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-103039