Skip to main content
VulnerabilityPublished Updated

CVE-2026-39726: Lumise Product Designer (WordPress plugin) · Cross-site Scripting

Affects Lumise Product Designer (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 2.1.4.1 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Patchstack)CVSS 3.17.1
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.4.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 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

Upgrade Lumise Product Designer (WordPress plugin) to 2.1.4.1.

Affected software

ProductAffectedFixed in
Lumise Product DesignerlumiseAffected
  • <2.1.4.1
Fixed in
  • 2.1.4.1

AI-suggested

Upgrade Lumise Product Designer to version 2.1.4.1 or later, where this vulnerability has been fixed. No additional mitigation steps are required once the official patch is applied.

Description

CVE-2026-39726 is a reflected Cross-site Scripting (XSS) vulnerability in Lumise Product Designer before version 2.1.4.1. It involves improper neutralization of input during web page generation, allowing an attacker to inject malicious scripts. This vulnerability has a high severity score of 7.1 and affects versions from initial releases up to but not including 2.1.4.1. A fix is available in version 2.1.4.1.

References

Community reviews

Loading reviews…