CVE-2026-121794 · Package
NO FIX YET · SEE WHAT TO DO
The Travelly tour booking plugin for WordPress and WooCommerce exposes stored payment gateway credentials, including PayPal API credentials and Stripe secret keys, in the HTML of the tour edit screen. An authenticated contributor-level user can view these secrets by viewing the page source, even though the modal that shows them is hidden.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Travelly plugin version 2.3.11 or earlier with WooCommerce payment gateways configured. Exposure requires an account with contributor-level access or higher, so sites with no untrusted contributor accounts face lower risk. Sites without this plugin or with no stored payment credentials can skip it.
Not affected if no-contributor-accounts, plugin-not-installed
Who cares self-hosted, travelly, woocommerce, wordpress
2.3.11 or lower in the WordPress plugins screenThe Travelly – Tour & Travel Booking Manager for WooCommerce plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.3.11 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to view stored WooCommerce payment gateway credentials — including PayPal API username, password, and signature, as well as Stripe test and live secret keys — injected verbatim into the HTML response of the tour edit screen. The credentials are present in the raw HTTP response regardless of the modal's CSS visibility state, making them trivially accessible by viewing page source.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.