# CVE-2026-107636: pH7Builder before 18.5.1 Payment Bypass via Payment Module MainController

> Attackers can bypass payment validation to obtain premium membership tiers by manipulating client-controlled fields, affecting pH7Builder users.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-32w5-672c-jvph

## What is CVE-2026-107636?

CVE-2026-107636 is a high-severity vulnerability in ph7software ph7builder, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

pH7Builder (pH7 Social Dating CMS) before 18.5.1 contains a payment validation vulnerability that allows registered low-privileged members to obtain any membership tier by supplying client-controlled plan and amount fields. Attackers can set item_number, cart_order_id, or the PayPal custom field while paying a token amount, or submit uncompleted PayPal IPN payments, to gain the most expensive membership and its paid features.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

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


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

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

## Is CVE-2026-107636 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107636 is a high-severity vulnerability in ph7software ph7builder, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107636 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-107636/ (Markdown: https://insights.sbomify.com/CVE-2026-107636/index.md)
```

## Sources

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

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