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

CVE-2026-56047

HIGH · 7.1 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 8 weeks old

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
Unauthenticated Cross Site Scripting (XSS) in perfmatters <= 2.6.3 versions.

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 · moderate confidence

Unauthenticated Cross Site Scripting (XSS) vulnerability in the perfmatters WordPress plugin affecting versions 2.6.3 and below. Attackers can inject malicious scripts without authentication, potentially compromising other users viewing affected pages.

MitigationUpdate perfmatters plugin to version 2.6.4 or later to receive the security patch. If immediate update is not possible, consider disabling the plugin temporarily until the patch can be 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 perfmatters plugin is installed
    Check your WordPress installation under wp-content/plugins/ for the perfmatters directory, or view the Plugins section in the WordPress admin dashboard
    Affected if The perfmatters directory exists in plugins folder
  2. Determine installed version of perfmatters
    Open the plugin file (perfmatters.php) or readme.txt in wp-content/plugins/perfmatters/ and locate the version declaration, or check the version column in WordPress admin > Plugins
    Affected if The version number displayed is 2.6.3 or lower
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify that perfmatters shows as 'Active' rather than 'Inactive' or 'Must-Use'
    Affected if The plugin status is Active and accessible to visitors without authentication
  4. Verify unauthenticated access is possible
    Confirm the site allows unauthenticated visitors to access pages where the perfmatters plugin renders output (the XSS is unauthenticated, meaning no login required)
    Affected if The website permits unauthenticated (logged-out) users to view pages

You are affected if the perfmatters plugin is installed, active, running version 2.6.3 or below, and your site allows unauthenticated visitors to access pages where the plugin executes

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 perfmatters plugin to version 2.6.4 or later to receive the security patch. If immediate update is not possible, consider disabling the plugin temporarily until the patch can be applied.

Recommended fix High confidence

Latest version of perfmatters plugin (newer than 2.6.3)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the perfmatters plugin
  4. Check if the current version is 2.6.3 or earlier
  5. If vulnerable, click 'Update Now' to update to the latest available version
  6. Alternatively, download the latest version from wordpress.org/plugins/perfmatters/ and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the new version number in the plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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