CVE-2026-108904

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

GHSA-3m9j-mmxr-3x76 ↗EUVD-2026-97067 ↗

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.5.0
fixed in 18.5.0
CWE-522 Insufficiently Protected Credentials
ETK-2026-1259Zero's internal tracking ID, independent of the CVE number., permanent identifier
9d 10h 29msince last run
47mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h19m
0
+2h
+6h
+8h
+10h
+12h

description

ph7builder releases before 18.5.0 may expose sensitive member records through API responses. An attacker with a valid private API key could obtain credential-related and authentication-secret data, potentially allowing account takeover or bypass of two-factor protections.

mitigation

Upgrade ph7builder to version 18.5.0 or later. Restrict and rotate private API keys that may have been exposed, and review affected accounts and authentication secrets.

fixed in 18.5.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.
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.32%23rd percentile
agent run time
47m
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

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-11 14:58Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1259",
  "cve_id": "CVE-2026-108904",
  "display_id": "CVE-2026-108904",
  "ghsa_id": "GHSA-3m9j-mmxr-3x76",
  "euvd_id": "EUVD-2026-97067",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Sensitive data exposure in ph7builder API responses",
  "summary": "ph7builder releases before 18.5.0 may expose sensitive member records through API responses. An attacker with a valid private API key could obtain credential-related and authentication-secret data, potentially allowing account takeover or bypass of two-factor protections.",
  "mitigation": "Upgrade ph7builder to version 18.5.0 or later. Restrict and rotate private API keys that may have been exposed, and review affected accounts and authentication secrets.",
  "vendor": "ph7software",
  "product": "ph7builder",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 18.5.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "18.5.0"
      ],
      "package_name": "ph7builder",
      "purl": null
    }
  ],
  "cwes": [
    522
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0032,
  "epss_percentile": 0.2306,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 46.6604551,
  "t0_at": "2026-10-11T14:58:06.113000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-11T14:58:06.113000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-11T14:58:06.113000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108904"
    }
  }
}

published 2026-10-11 18:30Z
last change 2026-10-21 04:45Z

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.