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

CVE-2026-1891

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-21
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 Simple Football Scoreboard plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ytmr_fb_scoreboard' shortcode in all versions up to, and including, 1.0 due to insufficient input sanitization and output escaping on user supplied attributes. 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 Simple Football Scoreboard WordPress plugin is vulnerable to stored XSS via the 'ytmr_fb_scoreboard' shortcode. Authenticated contributors+ can inject malicious JavaScript through unsanitized shortcode attributes, which then executes whenever users view pages containing the injected shortcode.

MitigationUpdate the plugin to a patched version once available; until then, restrict contributor-level access or disable the shortcode. The fix requires adding proper input sanitization (e.g., esc_attr()) and output escaping (e.g., esc_html(), esc_url()) to all user-supplied shortcode attributes.

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 Simple Football Scoreboard plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Simple Football Scoreboard' or check the plugin files in /wp-content/plugins/ for a folder containing 'football-scoreboard' or similar
    Affected if The plugin is installed and active
  2. Determine the installed plugin version
    In WordPress admin plugins list, click on the plugin name to view version details, or inspect the plugin's main PHP file for the 'Version' header in the plugin comments
    Affected if Version is at or below the last known vulnerable version (compare against current version on wordpress.org for reference)
  3. Identify usage of the vulnerable shortcode
    Search the WordPress database or use a plugin to search post content for the string '[ytmr_fb_scoreboard' across all posts, pages, and custom post types
    Affected if The shortcode is present in any published content
  4. Inspect shortcode attribute values for potential injection
    Examine the raw content of posts/pages containing the shortcode; check all attribute values (such as parameters like team names, colors, or any user-supplied values) for unescaped characters or script tags
    Affected if Attributes contain raw HTML, JavaScript, or special characters that should be escaped but are not
  5. Review user accounts with contributor+ access
    In WordPress admin, go to Users and filter by role to identify users with 'Contributor', 'Author', 'Editor', or 'Administrator' roles who can create or edit content containing shortcodes
    Affected if There are untrusted users with contributor-level or higher access who can add or modify shortcode-containing content

A user is affected if the Simple Football Scoreboard plugin is installed, the ytmr_fb_scoreboard shortcode is in use, and untrusted contributor+ users exist who could inject malicious JavaScript through unsanitized shortcode attributes.

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 a patched version once available; until then, restrict contributor-level access or disable the shortcode. The fix requires adding proper input sanitization (e.g., esc_attr()) and output escaping (e.g., esc_html(), esc_url()) to all user-supplied shortcode attributes.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.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-1891 — 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-1891 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