Atomic Edge analysis of CVE-2026-4871 (metadata-based): This vulnerability is a stored cross-site scripting (XSS) flaw in the Sports Club Management plugin for WordPress, affecting all versions up to and including 1.12.9. The issue exists in the `scm_member_data` shortcode’s ‘before’ and ‘after’ attributes, allowing authenticated attackers with Contributor-level access or higher to inject arbitrary web scripts. The CVSS score is 6.4 (Medium), with network attack vector, low complexity, and scope change.
Root Cause: Based on the CWE classification (79) and the vulnerability description, Atomic Edge analysis infers that the plugin’s `scm_member_data` shortcode does not properly sanitize or escape the ‘before’ and ‘after’ attributes before rendering HTML output. In WordPress, shortcode attributes are typically passed as strings; without adequate input sanitization (e.g., `wp_kses`, `sanitize_text_field`) and output escaping (e.g., `esc_attr`, `esc_html`), an attacker can inject malicious JavaScript or HTML. This conclusion is inferred from metadata; no code diff is available for confirmation.
Exploitation: An attacker with at least Contributor-level access can exploit this by embedding the `scm_member_data` shortcode in a post or page with a crafted ‘before’ or ‘after’ attribute. The attack vector uses the WordPress post editor (e.g., Classic Editor or Block Editor’s Custom HTML block). A typical payload for the ‘before’ attribute would be: `[scm_member_data before=”alert(‘XSS’)”]`. When any user (including administrators) views the affected post, the injected script executes in their browser. No AJAX or REST endpoint is needed; the attack occurs via standard post submission.
Remediation: The fix requires adding input sanitization and output escaping to the ‘before’ and ‘after’ attributes within the `scm_member_data` shortcode handler. Specifically, the plugin should apply `esc_attr()` to the attribute values when outputting them in HTML attributes, or sanitize them with `sanitize_text_field()` or `wp_kses_bad_protocol()` for more complex contexts. Developers should also consider using `wp_kses_allowed_html()` with an appropriate context to strip unsafe tags.
Impact: Successful exploitation allows attackers to inject persistent JavaScript that runs in the context of any user viewing the infected page. This can lead to session hijacking, credential theft, defacement, or redirection to malicious sites. Sensitive data such as cookies, authentication tokens, and page content can be exfiltrated. The stored nature of the XSS means the payload remains active until manually removed, affecting all visitors, including administrators.







