CVE-2026-14939: Visualizer (WordPress plugin) · Server-Side Request Forgery (SSRF)
Affects Visualizer (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.8 Medium : upgrade to 4.0.6 when convenient.
Data as of 2 Nov 2026, 10:57 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.6
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 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 2 Nov 2026.
What to do
Upgrade Visualizer (WordPress plugin) to 4.0.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Visualizer | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict Contributor-level user privileges where possible and monitor for suspicious activity related to SSRF attempts. Avoid exposing sensitive metadata endpoints to the WordPress environment. Follow vendor updates for patches addressing this issue.
Description
A Server-Side Request Forgery (SSRF) vulnerability exists in the Visualizer WordPress plugin before version 4.0.6. This flaw allows users with Contributor-level access or higher to supply URLs that are fetched server-side without restriction to safe address ranges. The vulnerability enables attackers to perform SSRF against link-local instance metadata endpoints, retrieving cloud instance metadata including IAM credentials. The attack is non-blind, as the fetched response is returned in the reply.