CVE-2026-96530: Optimole (WordPress plugin) · Information Exposure
Affects Optimole (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.2.15 when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.2.15
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 Optimole (WordPress plugin) to 4.2.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Optimole | Affected
| Fixed in
|
AI-suggested
Upgrade the Optimole plugin to version 4.2.15 or later where this issue is fixed. Since the vulnerability is due to missing capability checks, the official fix involves proper permission validation before displaying sensitive data. Patch status is not explicitly stated but the affected versions are prior to 4.2.15, indicating the fix is included in 4.2.15. Users should update promptly to remediate this exposure.
Description
The Optimole WordPress plugin before 4.2.15 does not perform a capability check before exposing its stored image-optimization account data in a dashboard widget, allowing any authenticated user, including Subscribers, to read the site's third-party service credentials.