dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4871

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Sports Club Management plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'before' and 'after' attributes of the `scm_member_data` shortcode in all versions up to, and including, 1.12.9 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Sports Club Management WordPress plugin has a stored XSS vulnerability in versions up to 1.12.9. The scm_member_data shortcode fails to properly sanitize the 'before' and 'after' attributes during input and escape them during output, allowing authenticated attackers with Contributor-level access to inject malicious JavaScript that executes for all users visiting affected pages.

MitigationUpdate the plugin to version 1.13.0 or later when available. As an interim measure, restrict Contributor-level user permissions and audit pages using the scm_member_data shortcode for malicious content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the Sports Club Management plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Sports Club Management' or check the plugin files in /wp-content/plugins/ for the sports-club-management folder. Check the plugin header for the version number.
    Affected if The plugin is installed and no security patches have been applied to the shortcode handling.
  2. Identify if the scm_member_data shortcode exists
    Search the plugin files (usually in main plugin PHP file) for 'add_shortcode' and verify 'scm_member_data' is registered. Also look for how 'before' and 'after' attributes are handled in the shortcode callback function.
    Affected if The shortcode exists and processes 'before'/'after' attributes without sanitize_text_field or esc_html/esc_attr.
  3. Check for posts or pages using the scm_member_data shortcode
    Search the WordPress database: SELECT * FROM wp_posts WHERE post_content LIKE '%scm_member_data%' AND post_status='publish'. Alternatively, use WP-CLI: wp post list --s="scm_member_data" --status=publish
    Affected if Published content exists that uses this shortcode with user-controlled 'before' or 'after' values.
  4. Audit user roles with Contributor-level access
    In WordPress admin, go to Users and review roles. Contributors can create posts but cannot publish. Check for any users with Contributor, Author, or Editor roles who may have added the malicious shortcode.
    Affected if There are users with Contributor-level or higher access who could have inserted malicious JavaScript via the shortcode attributes.
  5. Inspect shortcode output for missing escaping
    View source of a page containing the shortcode. Search for the 'before' and 'after' values in the HTML output. If unescaped characters like < > " appear literally in the HTML, the vulnerability is present.
    Affected if The 'before' and 'after' values render as raw HTML/JavaScript without HTML entity encoding.

A user is affected if the Sports Club Management plugin is installed, the scm_member_data shortcode is in use, and the output shows unescaped 'before' or 'after' attribute values or contributor-level users have added content with this shortcode.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.13.0 or later when available. As an interim measure, restrict Contributor-level user permissions and audit pages using the scm_member_data shortcode for malicious content.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4871 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4871 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data