Information ExposureWeakness · CWE-200

CVE-2026-7626

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-12

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · high confidence

The Slek Gateway for WooCommerce plugin v1.0 exposes merchant API credentials (slek_key and slek_secret) by embedding them directly into client-side HTML forms via the wsb_handle_slek_payment_redirect() function. Additionally, the slek_secret is transmitted as plaintext in GET parameters within IPN callback URLs. Unauthenticated attackers placing an order can extract these credentials from the HTML source or browser DevTools on the order-pay page.

MitigationThe plugin must be updated to handle credentials server-side only, removing all client-side credential exposure and avoiding secrets in URL parameters. Consider using server-side API calls and secure token-based authentication instead.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed plugin version

Navigate to WordPress admin > Plugins > Installed Plugins, locate 'Slek Gateway for WooCommerce', and note the version number displayed

Affected if version is 1.0 (the only affected version per this CVE)
Inspect order-pay page HTML for credentials

Place a test order on the site, proceed to the order-pay page (typically /order-pay/{order_id}/), right-click and view page source or open browser DevTools (F12), then search for 'slek_key' and 'slek_secret' in the HTML

Affected if slek_key or slek_secret values are present in the page source HTML (visible as form field values or in script tags)
Verify credentials in payment redirect form

On the order-pay page, locate any form that handles payment redirection. Inspect the form's HTML (right-click form > Inspect). Look for input fields with names containing 'slek_key' or 'slek_secret' and check if their 'value' attributes contain actual credential strings

Affected if form input fields contain exposed API credentials in their value attributes
Check IPN callback URLs for secrets in GET parameters

If available, locate any IPN (Instant Payment Notification) or webhook URL in the plugin settings or source code. Inspect the URL to see if 'slek_secret' or similar parameters are passed as GET query string parameters (e.g., ?slek_secret=...)

Affected if URLs contain slek_secret or other secret values as plaintext query parameters

A user is affected if they are running Slek Gateway for WooCommerce version 1.0 and their order-pay page exposes slek_key or slek_secret in HTML source or IPN callback URLs contain plaintext secrets in URL parameters.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

The plugin must be updated to handle credentials server-side only, removing all client-side credential exposure and avoiding secrets in URL parameters. Consider using server-side API calls and secure token-based authentication instead.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

13.0 hours of engineering $2,290

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-7626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7626 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-7626?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

Need this fixed?

Have this fixed 13 hrs · Moderate

Typical engagement from $2,290

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-7626 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References