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

CVE-2026-2936

HIGH · 7.2 CVSS v3.1 Published 2026-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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 Visitor Traffic Real Time Statistics plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'page_title' parameter in all versions up to, and including, 8.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an admin user accesses the Traffic by Title section.

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 Visitor Traffic Real Time Statistics WordPress plugin versions up to 8.4 fails to properly sanitize and escape the page_title parameter, allowing unauthenticated attackers to inject malicious JavaScript. This stored XSS payload executes whenever an administrator accesses the Traffic by Title admin section.

MitigationUpdate the plugin to a version beyond 8.4 once a patch is released. If no patch is available, disable the plugin. The fix requires implementing proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_html, esc_attr) on the page_title parameter throughout the codebase.

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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 plugin is installed and identify its version
    Access WordPress admin panel, navigate to Plugins > Installed Plugins, locate 'Visitor Traffic Real Time Statistics' and read the version number from the plugin description
    Affected if The installed version is 8.4 or lower (any version up to and including 8.4)
  2. Confirm the Traffic by Title feature is accessible
    Look for a 'Traffic by Title' or similar menu item in the plugin's admin dashboard navigation
    Affected if The Traffic by Title section exists and can be accessed by administrators
  3. Inspect stored page_title values for malicious content
    Examine the plugin's database tables (typically named similar to 'sts_visitor' or containing 'page_title' columns) or the plugin settings where page titles are stored, looking for unusual characters, script tags, or encoded JavaScript
    Affected if The database contains unsanitized HTML or JavaScript in any page_title field
  4. Review recent admin activity logs for suspicious submissions
    Check WordPress audit logs or server access logs for POST requests to the plugin's endpoint containing the page_title parameter with unusual content
    Affected if Recent requests show unauthenticated submissions to page_title with script tags or event handlers

You are affected if the plugin version is 8.4 or lower and the database contains any injected JavaScript or HTML in page_title fields, regardless of whether you have personally observed the XSS executing.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 8.4 once a patch is released. If no patch is available, disable the plugin. The fix requires implementing proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_html, esc_attr) on the page_title parameter throughout the codebase.

Recommended fix Moderate confidence

Latest version after 8.4 (typically 8.5 or higher)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Visitor Traffic Real Time Statistics' plugin
  4. 4. If an update is available, click 'Update Now' to update to the latest patched version
  5. 5. Alternatively, manually download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

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