# CVE-2026-7626: Information disclosure in Slek Gateway for WooCommerce

> Unauthenticated attackers can extract merchant API credentials from client-side HTML forms in the Slek Gateway for WooCommerce plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-2vh4-jqv5-4rjr

## What is CVE-2026-7626?

CVE-2026-7626 is a medium-severity vulnerability in qqqjus Slek Gateway for WooCommerce, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Slek Gateway for WooCommerce plugin for WordPress is vulnerable to Information Exposure in version 1.0. This is due to the wsb_handle_slek_payment_redirect() function placing the merchant's slek_key and slek_secret API credentials directly into a client-side HTML form, and additionally embedding the slek_secret as a plaintext GET parameter in the IPN callback URL. This makes it possible for unauthenticated attackers who can place an order on the affected store to extract the merchant's API credentials by viewing the HTML source or using browser DevTools on the WooCommerce order-pay page before the JavaScript auto-submit fires.

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

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


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

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

## Is CVE-2026-7626 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7626 is a medium-severity vulnerability in qqqjus Slek Gateway for WooCommerce, published on 12 May 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-7626 in the wild and no public exploit code.

Affected product: qqqjus Slek Gateway for WooCommerce. 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-7626/ (Markdown: https://insights.sbomify.com/CVE-2026-7626/index.md)
```

## Sources

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

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