CVE-2026-103039

validatedZero produced an exploit or a check.

EUVD-2026-113740 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Gravity Forms <= 3.1.2
CWE-502 Deserialization of Untrusted Data
ETK-2026-3049Zero's internal tracking ID, independent of the CVE number., permanent identifier
+23mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+23magent stopped
0
+5min
+10min
+15min
+20min
+25min

description

Gravity Forms through version 3.1.2 can deserialize attacker-controlled data submitted through certain List-type Post Custom Fields. An unauthenticated attacker may inject objects into post metadata when the affected field has a content template enabled; further impact, including code execution, requires additional environment-specific conditions.

mitigation

Disable public submission or remove content templates from List-type Post Custom Fields until an update is available. Review installed plugins and themes for usable object-deserialization chains, and apply a vendor release that fixes this issue when one is published.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 06:47Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-30 06:47Z
    cve_org: trigger signal, started the run
  2. 2026-10-30 07:10Z

this entry in the feed

GET /api/v1/feed/CVE-2026-103039

{
  "etk_id": "ETK-2026-3049",
  "cve_id": "CVE-2026-103039",
  "display_id": "CVE-2026-103039",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-113740",
  "status": "published",
  "anchor_state": "anchored",
  "title": "PHP object injection in Gravity Forms",
  "summary": "Gravity Forms through version 3.1.2 can deserialize attacker-controlled data submitted through certain List-type Post Custom Fields. An unauthenticated attacker may inject objects into post metadata when the affected field has a content template enabled; further impact, including code execution, requires additional environment-specific conditions.",
  "mitigation": "Disable public submission or remove content templates from List-type Post Custom Fields until an update is available. Review installed plugins and themes for usable object-deserialization chains, and apply a vendor release that fixes this issue when one is published.",
  "vendor": "Gravity Forms",
  "product": "Gravity Forms",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.1.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Gravity Forms",
      "purl": null
    }
  ],
  "cwes": [
    502
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.2833657333333333,
  "t0_at": "2026-10-30T06:47:32.599000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-30T07:10:40.161065+00:00",
      "days": 0.016059746122685185,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T06:47:32.599000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-30T06:47:32.599000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T06:47:32.599000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103039"
    }
  }
}

published 2026-10-30 07:10Z
last change 2026-10-30 08:07Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.