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

CVE-2026-4083

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 Scoreboard for HTML5 Games Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'scoreboard' shortcode in all versions up to, and including, 1.2. The shortcode function sfhg_shortcode() allows arbitrary HTML attributes to be added to the rendered <iframe> element, with only a small blacklist of four attribute names (same_height_as, onload, onpageshow, onclick) being blocked. While the attribute names are passed through esc_html() and values through esc_attr(), this does not prevent injection of JavaScript event handler attributes like onfocus, onmouseover, onmouseenter, etc., because these attribute names and simple JavaScript payloads contain no characters that would be modified by these escaping functions. The shortcode text is stored in post_content and is only expanded to HTML at render time, after WordPress's kses filtering has already been applied to the raw post content. 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 Scoreboard for HTML5 Games Lite WordPress plugin up to version 1.2 has a stored XSS vulnerability in the sfhg_shortcode() function. The function renders an iframe but only blacklists four attribute names (same_height_as, onload, onpageshow, onclick), allowing injection of other JavaScript event handlers like onfocus and onmouseover. While esc_html() and esc_attr() are applied, they don't filter event handler attribute names themselves. Stored XSS executes when pages are accessed.

MitigationUpdate the plugin to a version beyond 1.2 that implements proper attribute allowlisting or removes arbitrary attribute injection. Until then, remove or restrict the shortcode usage to trusted users only.

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. Confirm plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Scoreboard for HTML5 Games Lite'. Check the version number displayed below the plugin name.
    Affected if The plugin is installed and the version is 1.2 or lower (any version up to and including 1.2 is affected)
  2. Identify shortcode usage on the site
    Search the WordPress database or site content for the shortcode(s) used by this plugin. Common shortcodes may include [scoreboard], [html5_scoreboard], or similar. Can use WP-CLI: wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%scoreboard%'" or search plugin documentation.
    Affected if The shortcode is present in any post, page, or widget content on the site
  3. Inspect shortcode attributes in database content
    Examine the stored shortcode attributes in the database for suspicious event handler attributes. Look for attributes like onfocus, onmouseover, onblur, onerror, or other JavaScript event handlers that are not among the four blacklisted ones (same_height_as, onload, onpageshow, onclick).
    Affected if Any shortcode instance contains unsanitized event handler attributes like onfocus, onmouseover, or similar that could execute JavaScript
  4. Review rendered page output
    View a page containing the shortcode in a browser and inspect the HTML source (right-click > View Page Source). Look for iframe tags generated by the plugin and examine their attributes for injected JavaScript event handlers.
    Affected if The rendered iframe contains unexpected event handler attributes such as onfocus, onmouseover, onblur, or other JavaScript handlers

You are affected if the Scoreboard for HTML5 Games Lite plugin version 1.2 or lower is installed AND the plugin shortcode is being used on your site, allowing stored XSS execution when pages are viewed.

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 version beyond 1.2 that implements proper attribute allowlisting or removes arbitrary attribute injection. Until then, remove or restrict the shortcode usage to trusted users only.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4083 — 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-4083 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