# CVE-2026-16272: Client IP Spoofing via Untrusted HTTP Headers in PayTR's PayTR Virtual Pos iFrame API WHMCS Module

> Attackers can spoof client IP addresses via untrusted HTTP headers in the PayTR WHMCS module, bypassing security controls.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 9 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-g622-qgc4-8v95

## What is CVE-2026-16272?

CVE-2026-16272 is a critical vulnerability in PayTR Virtual Pos iFrame API WHMCS Module, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of less trusted source vulnerability in PayTR Payment and Electronic Money Institution Inc. PayTR Virtual Pos iFrame API WHMCS Module allows Exploitation of Trusted Identifiers.

This issue affects PayTR Virtual Pos iFrame API WHMCS Module: from v9.0.0 before v9.0.3.

Weakness: CWE-348 (Use of Less Trusted Source)

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


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

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

## Is CVE-2026-16272 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16272 is a critical vulnerability in PayTR Virtual Pos iFrame API WHMCS Module, published on 9 Sep 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-16272 in the wild and no public exploit code.

Affected product: PayTR Virtual Pos iFrame API WHMCS Module. 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-16272/ (Markdown: https://insights.sbomify.com/CVE-2026-16272/index.md)
```

## Sources

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

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