CVE-2026-120407

validatedZero produced an exploit or a check.

GHSA-q75w-p7rr-vmcf ↗EUVD-2026-124841 ↗

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.
Contact Form 7 < 6.2.5
fixed in 6.2.5
ETK-2026-4352Zero's internal tracking ID, independent of the CVE number., permanent identifier
+54mTTV
22mAI 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+54magent stopped
0
+15min
+30min
+45min
+60min

description

Contact Form 7 versions before 6.2.5 are affected. A user with the Editor role or higher can expose password hashes and sensitive user metadata from higher-privileged accounts when those users view and submit a form.

mitigation

Upgrade Contact Form 7 to version 6.2.5 or later. Restrict Editor-level access until the update is deployed.

fixed in 6.2.5

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 06:00Z
Δ 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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-11-13 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4352",
  "cve_id": "CVE-2026-120407",
  "display_id": "CVE-2026-120407",
  "ghsa_id": "GHSA-q75w-p7rr-vmcf",
  "euvd_id": "EUVD-2026-124841",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Sensitive user-data exposure in Contact Form 7",
  "summary": "Contact Form 7 versions before 6.2.5 are affected. A user with the Editor role or higher can expose password hashes and sensitive user metadata from higher-privileged accounts when those users view and submit a form.",
  "mitigation": "Upgrade Contact Form 7 to version 6.2.5 or later. Restrict Editor-level access until the update is deployed.",
  "vendor": null,
  "product": "Contact Form 7",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 6.2.5"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.2.5"
      ],
      "package_name": "Contact Form 7",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 22.127817866666668,
  "t0_at": "2026-11-13T06:00:07.477000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-13T06:53:49.697788+00:00",
      "days": 0.037294222083333335,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T06:00:07.477000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-13T06:00:07.477000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T06:00:07.477000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-120407"
    }
  }
}

published 2026-11-13 06:31Z
last change 2026-11-13 07:43Z

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.