CVE-2026-108905

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

GHSA-jfr6-f5qc-qp53 ↗EUVD-2026-97068 ↗

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.
ph7software ph7builder < 18.6.0
fixed in 18.6.0
CWE-798 Use of Hard-coded Credentials
ETK-2026-1252Zero's internal tracking ID, independent of the CVE number., permanent identifier
9d 12h 47msince last run
1h 41mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h01m
0
+4h
+6h
+8h
+10h
+12h

description

ph7builder versions before 18.6.0 contain an API access-control flaw associated with a built-in credential. An unauthenticated attacker able to submit requests with a forged Host header may bypass API checks and access sensitive member records.

mitigation

Upgrade ph7builder to version 18.6.0 or later. Until the upgrade is complete, restrict access to the affected API endpoints and enforce expected Host headers at a trusted reverse proxy.

fixed in 18.6.0

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.
–
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.
0.31%22nd percentile
agent run time
1h 41m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-11 14:58Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-11 14:58Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1252",
  "cve_id": "CVE-2026-108905",
  "display_id": "CVE-2026-108905",
  "ghsa_id": "GHSA-jfr6-f5qc-qp53",
  "euvd_id": "EUVD-2026-97068",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hard-coded API key access-control bypass in ph7builder",
  "summary": "ph7builder versions before 18.6.0 contain an API access-control flaw associated with a built-in credential. An unauthenticated attacker able to submit requests with a forged Host header may bypass API checks and access sensitive member records.",
  "mitigation": "Upgrade ph7builder to version 18.6.0 or later. Until the upgrade is complete, restrict access to the affected API endpoints and enforce expected Host headers at a trusted reverse proxy.",
  "vendor": "ph7software",
  "product": "ph7builder",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 18.6.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "18.6.0"
      ],
      "package_name": "ph7builder",
      "purl": null
    }
  ],
  "cwes": [
    798
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0031,
  "epss_percentile": 0.2203,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 101.3119687,
  "t0_at": "2026-10-11T14:58:06.784000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-11T14:58:06.784000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T14:58:06.784000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108905"
    }
  }
}

published 2026-10-11 15:18Z
last change 2026-10-21 05:31Z

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.