CVE-2026-4267
Reflected XSS in WordPress Query Monitor Plugin Allows Script Injection
Publication date: 2026-03-31
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| query_monitor | query_monitor | to 3.20.3 (inc) |
| wordsmith | query_monitor | to 3.20.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-4267 is a reflected Cross-Site Scripting (XSS) vulnerability in the Query Monitor plugin for WordPress, specifically in the Request panel. This vulnerability exists in all versions up to and including 3.20.3. It occurs because the plugin does not properly sanitize and escape user input from the '$_SERVER[REQUEST_URI]' parameter before displaying it. As a result, an unauthenticated attacker can inject arbitrary web scripts that execute in the context of a user's browser if the user is tricked into clicking a malicious link.
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute malicious scripts in the browsers of users who visit a crafted URL. Potential impacts include session hijacking, unauthorized actions performed on behalf of the user, theft of sensitive information, and other malicious activities that exploit the user's authenticated session or browser context.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability is a reflected Cross-Site Scripting (XSS) issue in the Query Monitor WordPress plugin's Request panel, exploitable via the '$_SERVER['REQUEST_URI']' parameter. Detection involves identifying attempts to inject malicious scripts through crafted URLs that appear in the request URI.
To detect exploitation attempts on your system or network, you can monitor web server logs for suspicious request URIs containing script tags or typical XSS payloads.
- Use grep or similar tools to search for suspicious patterns in access logs, for example: grep -iE "<script|%3Cscript|onerror|onload" /var/log/apache2/access.log
- Monitor HTTP requests with tools like Wireshark or tcpdump filtering for suspicious URL-encoded payloads.
- Use web application firewall (WAF) logs or rules to detect and block reflected XSS attempts targeting the Query Monitor plugin.
Note that the provided resources do not include specific detection commands or scripts for this vulnerability.
What immediate steps should I take to mitigate this vulnerability?
The immediate and recommended mitigation step is to update the Query Monitor WordPress plugin to version 3.20.4 or later, where the vulnerability has been fixed by properly escaping output to prevent reflected XSS.
If updating immediately is not possible, consider disabling or restricting access to the Query Monitor plugin, especially the Request panel, to trusted users only.
Additionally, implement or strengthen web application firewall (WAF) rules to detect and block reflected XSS payloads targeting the 'REQUEST_URI' parameter.
Regularly monitor your WordPress installation and plugins for security updates and apply them promptly.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The CVE-2026-4267 vulnerability is a reflected Cross-Site Scripting (XSS) flaw in the Query Monitor WordPress plugin that allows unauthenticated attackers to inject arbitrary web scripts. Such vulnerabilities can lead to unauthorized actions or session hijacking, which may result in unauthorized access to user data or manipulation of user sessions.
While the provided context does not explicitly mention compliance with standards like GDPR or HIPAA, reflected XSS vulnerabilities generally pose risks to data confidentiality and integrity. This can potentially lead to non-compliance with regulations that require protection of personal data and secure handling of user interactions.
Therefore, organizations using affected versions of the Query Monitor plugin should consider this vulnerability a risk to compliance frameworks that mandate secure coding practices and protection against client-side attacks.