CVE-2026-120207

waiting for further signalsZero needs more public information before it can validate it.

GHSA-h2jf-7chq-2q39 ↗EUVD-2026-114728 ↗

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.
Thelia Page Module < 2.0.4
fixed in 2.0.4
ETK-2026-3196Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 03msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+6h26m
0
+2h
+4h
+8h
+10h
+12h

description

Thelia Page Module versions before 2.0.4 are affected by cross-site request forgery in back-office deletion functions. An attacker may cause deletion of page-related tags, documents, or images if a logged-in administrator is induced to make a request.

mitigation

Upgrade Thelia Page Module to version 2.0.4 or later. Restrict back-office access to trusted administrators until the update is applied.

fixed in 2.0.4

check
no
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.
contextual
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
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-31 17:25Z
Δ 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-31 17:25Z
    ghsa: trigger signal, started the run
  2. 2026-10-31 17:25Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3196",
  "cve_id": "CVE-2026-120207",
  "display_id": "CVE-2026-120207",
  "ghsa_id": "GHSA-h2jf-7chq-2q39",
  "euvd_id": "EUVD-2026-114728",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-site request forgery in Thelia Page Module",
  "summary": "Thelia Page Module versions before 2.0.4 are affected by cross-site request forgery in back-office deletion functions. An attacker may cause deletion of page-related tags, documents, or images if a logged-in administrator is induced to make a request.",
  "mitigation": "Upgrade Thelia Page Module to version 2.0.4 or later. Restrict back-office access to trusted administrators until the update is applied.",
  "vendor": "Thelia",
  "product": "Thelia Page Module",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.0.4"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.0.4"
      ],
      "package_name": "Thelia Page Module",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 26.2404246,
  "t0_at": "2026-10-31T17:25:54.837000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-31T17:25:54.837000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T17:25:54.837000+00:00",
      "url": "https://github.com/advisories/GHSA-h2jf-7chq-2q39"
    }
  }
}

published 2026-10-31 19:04Z
last change 2026-11-01 02:28Z

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.