# CVE-2026-96255: Payments for Hubtel < 1.0.2 - Unauthenticated Payment Gateway Credentials Disclosure via Debug Log

> Unauthenticated attackers can access debug logs to steal payment gateway API credentials, compromising financial data and accounts.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-gv9c-r7rv-4q3q

## What is CVE-2026-96255?

CVE-2026-96255 is a high-severity vulnerability in Unknown Payments for Hubtel, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Payments for Hubtel WordPress plugin before 1.0.2 does not prevent public access to a debug log in which it records payment requests, including the store's payment gateway API credentials in plain text, allowing unauthenticated attackers to obtain those credentials.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-96255 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96255 is a high-severity vulnerability in Unknown Payments for Hubtel, published on 1 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-96255 in the wild and no public exploit code.

Affected product: Unknown Payments for Hubtel. 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-96255/ (Markdown: https://insights.sbomify.com/CVE-2026-96255/index.md)
```

## Sources

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

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