Security readout for executives and security teams
Plain-English summary
A logged-in WordPress user with subscriber-level access may be able to run code on sites using Query Wrangler through version 1.5.57. Successful exploitation could expose data, alter the site, or disrupt service. The supplied sources do not establish active exploitation or identify a confirmed fixed version.
Executive priority
Treat this as an immediate priority for exposed WordPress environments. Rapidly identify affected installations, reduce subscriber access, and apply authoritative remediation when confirmed. The potential impact is site and server compromise, but active exploitation is not established by the supplied evidence.
Technical view
CVE-2026-73992 is classified as CWE-94 code injection with CVSS 3.1 score 9.9. The vector indicates network access, low complexity, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. The reported affected range is Query Wrangler <=1.5.57, although the structured affected record is inconsistent.
Likely exposure
Exposure is most likely on internet-accessible WordPress sites running Query Wrangler 1.5.57 or earlier where an attacker can obtain subscriber-level access. Sites without the plugin, or with versions outside the reported range, are not established as affected by the supplied evidence.
Exploitation context
The vulnerability reportedly requires a low-privileged authenticated account and no victim interaction. The CVSS vector supports remote, low-complexity exploitation with potentially complete compromise. KEV status is false, and the supplied sources provide no evidence of exploitation in the wild.
Researcher notes
The title and description identify versions <=1.5.57, but the structured affected entry lists versions as “n/a” and default status as unaffected. This inconsistency warrants confirmation before definitive fleet-wide conclusions. No exploit mechanics, fixed version, vendor advisory, or observed exploitation evidence appears in the supplied bundle.
Mitigation direction
- Inventory WordPress sites for Query Wrangler and record installed versions.
- Check Patchstack and vendor guidance for a confirmed fixed release or official mitigation.
- Prioritize sites running version 1.5.57 or earlier for immediate containment.
- If no verified fix exists, consider disabling the plugin until authoritative guidance is available.
- Review whether public subscriber registration or unnecessary subscriber accounts can be restricted.
Validation and detection
- Confirm whether Query Wrangler is installed and determine its exact version.
- Identify sites allowing subscriber registration or containing untrusted subscriber accounts.
- Review WordPress, web server, and security logs for unexplained privileged actions or code execution.
- After remediation, verify the affected plugin version is absent or replaced by a confirmed safe release.
- Monitor the CVE and Patchstack records for corrected affected-version and remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-73992 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/query-wrangler/vulnerability/wordpress-query-wrangler-plugin-1-5-57-remote-code-execution-rce-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code
Improper Control of Generation of Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.