CVE-2026-119643 in MembershipWorks Plugininfo

Summary

by MITRE • 11/17/2026

The MembershipWorks - Membership, Events & Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 6.17. This is due to insufficient output escaping on member-supplied data retrieved from the MembershipWorks SaaS API in the sf_shortcode(), sf_widget_event_do(), and sf_widget_folder_do() functions, where the 'nam' (member name), 'ttl' (event title), 'url', 'adn' (venue name), 'szp', and 'ezp' fields are output into page HTML without escaping, or, in sf_widget_folder_do(), placed in an image alt attribute that an onerror handler copies into innerHTML. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/17/2026

The MembershipWorks plugin for WordPress, which facilitates membership management, event coordination, and directory services, contains a critical security flaw affecting all versions up through 6.17. This vulnerability is classified as Stored Cross-Site Scripting, commonly referred to by the industry standard CWE-80. The root cause lies in insufficient output escaping mechanisms within specific PHP functions that handle data retrieved from the MembershipWorks Software-as-a-Service API. Specifically, the sf_shortcode(), sf_widget_event_do(), and sf_widget_folder_do() functions fail to properly sanitize or encode member-supplied data before rendering it into HTML content. This lack of sanitization allows malicious actors to inject executable JavaScript code directly into the application's output stream.

The technical execution of this vulnerability relies on several specific input fields that are rendered without adequate protection. These include the nam field representing member names, ttl for event titles, url links, adn for venue names, and additional parameters such as szp and ezp. In most instances, these values are inserted directly into page HTML structures where they remain unescaped. A particularly dangerous aspect of this flaw is observed in the sf_widget_folder_do function, which places data into an image alt attribute. Attackers can exploit standard DOM parsing behaviors by embedding malicious JavaScript within the onerror handler of an image tag. When a browser attempts to load a broken or non-existent image source specified by the attacker, it triggers the onerror event, causing the injected script contained in the alt text to execute via innerHTML manipulation. This technique effectively bypasses basic HTML attribute escaping checks that might otherwise prevent direct script injection.

The operational impact of this vulnerability is severe due to its stored nature and unauthenticated access vector. Because the malicious scripts are saved within the application's data store, they persist on the server side rather than being limited to a single user session or request parameter. This means that any authenticated administrator or member who views pages containing these compromised elements will have their browser execute the injected code in the context of the vulnerable site. Attackers can leverage this capability to perform actions such as stealing administrative credentials through cookie theft, hijacking active sessions, performing unauthorized account modifications, defacing websites, or redirecting users to phishing sites. The ability for unauthenticated attackers to trigger these conditions means that simply visiting a page with embedded malicious content is sufficient to compromise the user's interaction with the application.

From a threat intelligence perspective, this vulnerability aligns with MITRE ATT&CK techniques related to Client-Side Scripting Injection and potentially Credential Access via Browser Harvesting if session tokens are targeted. The persistence of the payload classifies it under Persistence mechanisms where malicious content remains in the system until manually removed or overwritten by legitimate updates. To mitigate this risk, organizations must immediately upgrade MembershipWorks to version 6.18 or later, which addresses these escaping deficiencies. In environments where upgrading is not immediately feasible, administrators should implement strict Content Security Policy headers to restrict script execution sources and consider deploying web application firewalls that can detect and block common XSS payloads in HTTP responses. Regular security audits focusing on output encoding practices for all data retrieved from external APIs are also recommended to prevent similar vulnerabilities in other plugins or custom code modules.

Responsible

Wordfence

Reservation

10/30/2026

Disclosure

11/17/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!