CVE-2026-96565 · Package
NO FIX YET · SEE WHAT TO DO
The WP-Members Membership plugin for WordPress, in versions up to and including 3.5.7, does not sanitize or escape a WooCommerce classic checkout multicheckbox/multiselect field. An authenticated subscriber can store scripts that run in the browser of any user who opens the affected page.
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.
Sites running the WP-Members Membership plugin at version 3.5.7 or older together with WooCommerce's classic checkout using its multicheckbox or multiselect fields. The sibling registration, profile and account-edit handlers fail closed on this input, so exposure is limited to the checkout path. Sites without WooCommerce or without the plugin can skip it.
Not affected if no-woocommerce, no-wp-members, version-above-3.5.7
Who cares self-hosted, woocommerce, wordpress, wp-members
wp-content/plugins/wp-members/, and see whether it is 3.5.7 or older.3.5.7 (the fixed version is not named in the sources).The WP-Members Membership Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via WooCommerce Checkout Multicheckbox/Multiselect Field (scalar bypass of wpmem_sanitize_array) in all versions up to, and including, 3.5.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only exploitable via the WooCommerce classic checkout path, as the sibling registration, profile, and account-edit handlers implode the value before sanitization, which raises a PHP 8 TypeError on scalar input and fails closed.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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.