# CVE-2026-37604: Security feature bypass in n/a

> Attackers bypass IP-based login throttling in pH7Builder by spoofing X-Forwarded-For headers, enabling brute-force attacks against admin accounts.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-f42g-42x9-p8pf

## What is CVE-2026-37604?

CVE-2026-37604 is a medium-severity vulnerability in n/a, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pH7Software pH7Builder (pH7 Social Dating CMS) through 18.2.0 resolves the client IP address in _protected/framework/Ip/Ip.class.php from the HTTP_CLIENT_IP and HTTP_X_FORWARDED_FOR headers without verifying the request comes from a trusted proxy. Because the admin login attempt counter and lockout are keyed on this value, a remote unauthenticated attacker bypasses IP-based throttling by sending a different X-Forwarded-For value per request

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-37604 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-37604 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-37604 is a medium-severity vulnerability in n/a, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-37604 exists.

Affected product: n/a. 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-37604/ (Markdown: https://insights.sbomify.com/CVE-2026-37604/index.md)
```

## Sources

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

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