CVE-2026-111579

validatingZero is analyzing and reversing it now.

GHSA-59qc-m59w-2g85 ↗

no check availablenot proven exploitable
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.
Forminator Forms >= 1.58.0, < 1.58.4
fixed in 1.58.4
ETK-2026-4145Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Forminator Forms versions before 1.58.4 may allow unauthenticated visitors to register through payment-gated user-registration forms without completing payment. The issue applies when the form's payment gateway was configured previously but is later disconnected or unavailable, and the resulting account may receive the role configured by the form.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Update Forminator Forms to version 1.58.4 or later. Until updated, disable affected payment-gated registration forms and review configured registration roles, especially administrative roles.

fixed in 1.58.4

check
building now
exploit
not yet
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.
–
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
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 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

Run in progress: no artifact yet.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-4145",
  "cve_id": "CVE-2026-111579",
  "display_id": "CVE-2026-111579",
  "ghsa_id": "GHSA-59qc-m59w-2g85",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Server-side payment enforcement bypass in Forminator Forms",
  "summary": "Forminator Forms versions before 1.58.4 may allow unauthenticated visitors to register through payment-gated user-registration forms without completing payment. The issue applies when the form's payment gateway was configured previously but is later disconnected or unavailable, and the resulting account may receive the role configured by the form.",
  "mitigation": "Update Forminator Forms to version 1.58.4 or later. Until updated, disable affected payment-gated registration forms and review configured registration roles, especially administrative roles.",
  "vendor": null,
  "product": "Forminator Forms",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.58.0, < 1.58.4"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.58.4"
      ],
      "package_name": "Forminator Forms",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-11T06:00:06.690000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T06:00:06.690000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T06:00:06.690000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111579"
    }
  }
}

published 2026-11-11 06:31Z
last change 2026-11-11 06:34Z

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.