CVE-2026-93370 · Package
NO FIX YET
The Paystack WooCommerce Payment Gateway plugin for WordPress, up to and including 5.8.5, leaks customer personal data through the 'key' parameter. An unauthenticated attacker can enumerate sequential order IDs and read billing name, email, phone, addresses and purchased products embedded in page HTML.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Only WooCommerce stores running the Paystack payment gateway plugin at version 5.8.5 or earlier, and only where the merchant has enabled the optional custom metadata feature in the Paystack gateway settings. Stores with that feature off, or on a newer plugin version, are not exposed according to the sources. The exposure is through page HTML generated from sequential order IDs.
Not affected if custom-metadata-disabled, newer-plugin-version
Who cares payments, paystack, woocommerce, wordpress
5.8.5 are affected.No fix yet, per the sources.
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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.