Skip to main content
VulnerabilityPublished Updated

CVE-2026-16032: LWS Optimize (WordPress plugin) · Cross-Site Scripting (XSS)

Affects LWS Optimize (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.1.2 when convenient.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Aug 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 8 Nov 2026.

What to do

Upgrade LWS Optimize (WordPress plugin) to 4.1.2.

Affected software

ProductAffectedFixed in
LWS OptimizeAffected
  • <4.1.2
Fixed in
  • 4.1.2

AI-suggested

Until then, restricting access to the administrative dashboard and limiting exposure of the analytics endpoint may reduce risk.

Description

The LWS Optimize WordPress plugin before 4.1.2 does not properly escape a value submitted through an unauthenticated analytics endpoint before storing it and rendering it in an administrative dashboard, allowing unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the affected dashboard page.

References

Community reviews

Loading reviews…