Is johnbillion/query-monitor 3.10 vulnerable?
Composer · 2 releases from 3.10.0 to 3.10.1 · latest johnbillion/query-monitor is 4.1.1 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. johnbillion/query-monitor 3.10.1, the last 3.10 release, is affected by 1 known security advisory (1 medium), including CVE-2026-4267. Upgrade to 3.20.4 or later to fix all of them.
composer require johnbillion/query-monitor:^3.20.4Is your project on an affected johnbillion/query-monitor?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting johnbillion/query-monitor 3.10.1
The Query Monitor plugin for WordPress has Reflected Cross-Site Scripting via Request URI
- Affected
- <3.20.4
- Fixed in
- 3.20.4
Every johnbillion/query-monitor 3.10.x release
Affected: 3.10.0 to 3.10.1. Latest johnbillion/query-monitor: 4.1.1.
| Version | Known advisories |
|---|---|
| johnbillion/query-monitor 3.10.1 | CVE-2026-4267 |
| johnbillion/query-monitor 3.10.0 | CVE-2026-4267 |
Which of your client projects are still on johnbillion/query-monitor 3.10?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact johnbillion/query-monitor version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other johnbillion/query-monitor versions
- johnbillion/query-monitor 3.13
- johnbillion/query-monitor 3.12
- johnbillion/query-monitor 3.11
- johnbillion/query-monitor 3.9
- johnbillion/query-monitor 3.8
- johnbillion/query-monitor 3.7
- johnbillion/query-monitor 4.1
- johnbillion/query-monitor 4.0
- johnbillion/query-monitor 3.20
- johnbillion/query-monitor 3.19
- johnbillion/query-monitor 3.18
- johnbillion/query-monitor 3.17
- All johnbillion/query-monitor advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.