Live › vulnerability › CVE-2026-109972
Go to dashboardThe s2Member WordPress membership plugin fails to sanitize the date_format parameter, so a contributor-level user can save a payload that renders as HTML on pages. When a visitor opens an affected page, the injected script runs in their browser.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 07:31 UTC. All times on this page are UTC.
Sites running the s2Member plugin at version 261011 or earlier where contributor-level or higher users can create or edit pages. Sites without s2Member, or where only trusted administrators can write content, face much less exposure.
No product ranges from the sources yet.
wp plugin get s2member --field=version261011 once the vendor releases a fixed build (fixed version not stated in the sources)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The s2Member – Excellent for All Kinds of Memberships, Content Restriction Paywalls & Member Access Subscriptions plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'date_format' parameter in all versions up to, and including, <= 261011 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload bypasses wp_kses_post() on save because it contains no literal angle brackets — only backslash-escaped sequences that PHP's date() materializes into HTML tag characters at render time after WordPress's shortcode_parse_atts() applies stripcslashes() to the attribute value.
This page as .md · .json · in your agent: get_signal("CVE-2026-109972")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.