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

CVE-2026-4267

HIGH · 7.2 CVSS v3.1 Published 2026-03-31
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 Query Monitor – The developer tools panel for WordPress plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘$_SERVER['REQUEST_URI']’ parameter in all versions up to, and including, 3.20.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

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 Query Monitor WordPress plugin fails to sanitize and escape the $_SERVER['REQUEST_URI'] parameter before outputting it, creating a reflected XSS vulnerability in versions up to 3.20.3. Unauthenticated attackers can craft malicious URLs that inject arbitrary JavaScript, which executes when users click specially crafted links.

MitigationUpdate Query Monitor plugin to version 3.20.4 or later. As an interim measure, implement web application firewall rules to filter malicious REQUEST_URI patterns.

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. Confirm Query Monitor plugin is installed
    Check the plugin directory wp-content/plugins/query-monitor/ or run 'wp plugin list' via WP-CLI
    Affected if Query Monitor plugin files exist in the WordPress installation
  2. Determine installed version
    Read the main plugin file (query-monitor.php) and check the Version header in the plugin comment block, or run 'wp plugin list --verbose'
    Affected if Version is 3.20.3 or lower (any version up to and including 3.20.3)
  3. Verify plugin is active
    Check WordPress admin/plugins.php or run 'wp plugin status query-monitor'
    Affected if Plugin status shows as 'Active'
  4. Check for vulnerable REQUEST_URI output
    Search plugin PHP files for patterns like echo $_SERVER['REQUEST_URI'] or print $_SERVER['REQUEST_URI'] without sanitization functions such as esc_url(), esc_attr(), or htmlspecialchars()
    Affected if Found instances of unsanitized REQUEST_URI output in the plugin code
  5. Confirm site accessibility
    Verify the WordPress site is publicly accessible without authentication requirements
    Affected if Site is accessible to unauthenticated users (no login required to trigger the vulnerability)

The environment is affected if Query Monitor plugin versions 3.20.3 or lower is installed, active, and contains unsanitized REQUEST_URI output that can be triggered by unauthenticated users via crafted URLs.

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 Query Monitor plugin to version 3.20.4 or later. As an interim measure, implement web application firewall rules to filter malicious REQUEST_URI patterns.

Recommended fix Moderate confidence

Query Monitor version 3.20.4 or latest available version (versions after 3.20.3 contain the fix)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Query Monitor' in the plugin list
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, navigate to Dashboard > Updates and select Query Monitor to update
  6. Verify the update completed successfully by checking the plugin version after updating

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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