# CVE-2026-108905: pH7Builder before 18.6.0 Hard-Coded API Key Bypass via Host Header

> Unauthenticated attackers can bypass API checks using a hard-coded key and spoofed Host header to access sensitive member data in pH7Builder.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-jfr6-f5qc-qp53

## What is CVE-2026-108905?

CVE-2026-108905 is a high-severity vulnerability in ph7software ph7builder, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pH7Builder (pH7 Social Dating CMS) before 18.6.0 contains a hard-coded API key vulnerability in Tool.class.php that allows unauthenticated attackers to bypass API access checks by spoofing the Host header. Attackers can send Host: localhost with private_api_key=dev772277 and the default allowed URL to retrieve member emails, IP addresses, phone numbers, and bank account fields.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-108905?


## How do I fix CVE-2026-108905?

No fix has been published for CVE-2026-108905 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108905 being exploited?

There is no known exploitation of CVE-2026-108905 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108905 and fix it if it is affected.

What it is: CVE-2026-108905 is a high-severity vulnerability in ph7software ph7builder, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108905 in the wild and no public exploit code.

Affected product: ph7software ph7builder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-108905/ (Markdown: https://insights.sbomify.com/CVE-2026-108905/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108905
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108905
- OSV: https://osv.dev/vulnerability/CVE-2026-108905

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108905/
Summaries are generated and may contain mistakes; the official description above is the record.