Skip to main content
CVE-2026-107710VulnerabilityPublished

The Hustle – Email Marketing, Lead Generation, Optins, Popups plugin for WordPress is vulnerable to Stored Cross-Site

Source GCVE Database

0
Authoritative record:CVE-2026-107710· Medium 6.4

Not known to be exploited · CVSS 6.4 Medium.

Data as of 28 Oct 2026, 10:42 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
wpmudevHustle – Email Marketing, Lead Generation, Optins, PopupsAffected
  • <=7.8.14.3
Fixed in–

AI-suggested

Administrators should review and restrict the assignment of 'Create and Update Modules' permissions within The Hustle plugin's Settings → Permissions to trusted roles only. Monitor the vendor's advisory channels for any forthcoming patches or updates addressing this vulnerability.

Description

The Hustle plugin for WordPress, used for email marketing and lead generation, contains a stored cross-site scripting (XSS) vulnerability in the 'content[title]' parameter. This affects all versions up to and including 7.8.14.3. The flaw arises from insufficient input sanitization and output escaping, allowing authenticated users with custom-level access and the 'Create and Update Modules' capability to inject malicious scripts. This capability is not granted by default and must be explicitly assigned by an administrator via the plugin's permissions settings.

References

Community reviews

Loading reviews…