CVE-2026-111908

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

GHSA-cwqc-qp2c-47mg ↗EUVD-2026-103312 ↗

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.
thorsten phpMyFAQ >= 4.0.0, < 4.1.9; >= 4.2.0-alpha, < 4.2.0-beta
fixed in 4.1.9, 4.2.0-beta
ETK-2026-1910Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 00h 13msince last run
54mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h20m
0
+2h
+6h
+8h
+10h
+12h

description

phpMyFAQ versions 4.0.0 through 4.1.8, and 4.2.0-alpha releases before 4.2.0-beta, do not enforce per-FAQ access checks during updates. An authenticated user granted FAQ editing rights can alter restricted FAQ entries, including their content and publication status, if they can target those entries.

mitigation

Upgrade stable deployments to phpMyFAQ 4.1.9 or later, and upgrade 4.2.0-alpha deployments to 4.2.0-beta or later. Until upgraded, restrict the global FAQ-editing permission to trusted users.

fixed in 4.1.9, 4.2.0-beta

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.29%20th percentile
agent run time
54m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-17 18:46Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-1910",
  "cve_id": "CVE-2026-111908",
  "display_id": "CVE-2026-111908",
  "ghsa_id": "GHSA-cwqc-qp2c-47mg",
  "euvd_id": "EUVD-2026-103312",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Broken object-level authorization in phpMyFAQ FAQ updates",
  "summary": "phpMyFAQ versions 4.0.0 through 4.1.8, and 4.2.0-alpha releases before 4.2.0-beta, do not enforce per-FAQ access checks during updates. An authenticated user granted FAQ editing rights can alter restricted FAQ entries, including their content and publication status, if they can target those entries.",
  "mitigation": "Upgrade stable deployments to phpMyFAQ 4.1.9 or later, and upgrade 4.2.0-alpha deployments to 4.2.0-beta or later. Until upgraded, restrict the global FAQ-editing permission to trusted users.",
  "vendor": "thorsten",
  "product": "phpMyFAQ",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0, < 4.1.9"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.1.9"
      ],
      "package_name": "phpMyFAQ",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.2.0-alpha, < 4.2.0-beta"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.2.0-beta"
      ],
      "package_name": "phpMyFAQ",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L",
  "epss_score": 0.0029,
  "epss_percentile": 0.2061,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 54.32612405,
  "t0_at": "2026-10-17T18:46:26.780000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-17T18:46:26.780000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-17T18:46:26.780000+00:00",
      "url": "https://github.com/advisories/GHSA-cwqc-qp2c-47mg"
    }
  }
}

published 2026-10-17 22:11Z
last change 2026-10-21 23:09Z

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.