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

CVE-2026-4303

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 WP Visitor Statistics (Real Time Traffic) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wsm_showDayStatsGraph' shortcode in all versions up to, and including, 8.4 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 WP Visitor Statistics plugin for WordPress contains a Stored XSS vulnerability in the 'wsm_showDayStatsGraph' shortcode (versions up to 8.4). The vulnerability stems from insufficient input sanitization and output escaping on user-supplied attributes, allowing authenticated attackers with contributor-level access or higher to inject arbitrary JavaScript that executes whenever users view pages containing the malicious shortcode.

MitigationUpdate the WP Visitor Statistics plugin to a version beyond 8.4 that includes proper input sanitization and output escaping for shortcode attributes. Alternatively, restrict contributor-level user permissions until the patch is applied.

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 WP Visitor Statistics plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Visitor Statistics (Real Time Traffic)' or 'wp-stats-manager'. Check the version number displayed under the plugin name.
    Affected if Plugin is installed with version 8.4 or lower
  2. Identify usage of the vulnerable shortcode
    Search your WordPress database for 'wsm_showDayStatsGraph' shortcode usage. You can use phpMyAdmin to query wp_posts for post_content containing '[wsm_showDayStatsGraph' or check your pages/posts via admin interface.
    Affected if The shortcode wsm_showDayStatsGraph is present in any published content
  3. Review user role permissions
    In WordPress admin, go to Users > All Users and check which users have Contributor, Author, Editor, or Administrator roles. These roles can create or edit content containing shortcodes.
    Affected if Any user account with Contributor-level access or higher exists on the site (which is typical for multi-user installations)
  4. Confirm shortcode accepts user-supplied attributes
    The vulnerability exists in how the plugin handles attributes passed to [wsm_showDayStatsGraph]. If your site allows users to add custom attribute values to this shortcode, inspect the rendered HTML to verify if those attributes are properly escaped.
    Affected if Users can insert the shortcode with custom attribute values that appear unescaped in page source

You are affected if the WP Visitor Statistics plugin version is 8.4 or earlier AND the wsm_showDayStatsGraph shortcode is in use on your site, allowing authenticated users with contributor access or higher to inject malicious scripts.

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 WP Visitor Statistics plugin to a version beyond 8.4 that includes proper input sanitization and output escaping for shortcode attributes. Alternatively, restrict contributor-level user permissions until the patch is applied.

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-4303 — 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-4303 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