Is johnbillion/query-monitor 3.20 vulnerable?

Composer · 5 releases from 3.20.0 to 3.20.4 · latest johnbillion/query-monitor is 4.1.1 · checked 18 Nov 2026

No known advisories in the last release

johnbillion/query-monitor 3.20.4, the last 3.20 release, has no known advisories. 1 advisory affects earlier 3.20.x releases, so update to 3.20.4.

Update within 3.20:composer require johnbillion/query-monitor:^3.20.4

Is your project on an affected johnbillion/query-monitor?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 3.20.x, affecting earlier releases

  • MediumCVE-2026-4267GHSA-2xr4-chcf-vmvf19 Mar 2026

    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.20.x release

Affected: 3.20.0 to 3.20.3. 3.20.4 is not affected. Latest johnbillion/query-monitor: 4.1.1.

VersionKnown advisories
johnbillion/query-monitor 3.20.4None
johnbillion/query-monitor 3.20.3CVE-2026-4267
johnbillion/query-monitor 3.20.2CVE-2026-4267
johnbillion/query-monitor 3.20.1CVE-2026-4267
johnbillion/query-monitor 3.20.0CVE-2026-4267

Which of your client projects are still on johnbillion/query-monitor 3.20?

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

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.