Skip to main content
VulnerabilityPublished

CVE-2026-120119: HUSKY (WordPress plugin) · SQL Injection

Affects HUSKY (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 21 Nov 2026, 09:45 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.16.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
realmag777HUSKY – Products Filter for WooCommerce Professional. MCP is onboardAffected
  • <=1.4.7
Fixed in–

AI-suggested

Users should monitor the vendor's advisory channels for updates. In the meantime, restricting subscriber-level access or disabling the affected plugin until a fix is available may reduce risk. Since the exploit requires a valid product_messenger nonce obtainable via AJAX, limiting access to AJAX endpoints or shortcode attributes may provide temporary mitigation.

Description

The HUSKY – Products Filter for WooCommerce Professional plugin for WordPress contains a time-based SQL Injection vulnerability in versions up to and including 1.4.7. This flaw arises from insufficient escaping of the 'link' parameter (specifically the inner 'woof_text' query parameter) and inadequate preparation of the SQL query. Authenticated users with subscriber-level access or higher can exploit this vulnerability to append SQL queries and extract sensitive database information. Exploitation requires a valid product_messenger nonce, which can be easily obtained by any logged-in user due to the way the nonce is issued via an AJAX endpoint and the shortcode's attributes.

References

Community reviews

Loading reviews…