VulnerabilityPublished 4 Nov 2026

CVE-2026-110692: PowerPack Addons for Elementor: Widgets, Form Styler and Templates (WordPress plugin) · Server-Side Request Forgery

Affects PowerPack Addons for Elementor: Widgets, Form Styler and Templates (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited : upgrade to 3.1.3 soon.

Data as of 4 Nov 2026, 06:28 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 3.1.3

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 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 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade PowerPack Addons for Elementor: Widgets, Form Styler and Templates (WordPress plugin) to 3.1.3.

Affected software

Product	Affected	Fixed in
PowerPack Addons for Elementor: Widgets, Form Styler and Templates	Affected >=2.10.0 <3.1.3	Fixed in 3.1.3

AI-suggested

Upgrade the PowerPack Addons for Elementor plugin to version 3.1.3 or later, where the vulnerability is fixed. No other mitigation is indicated by the vendor advisory.

Description

A Server-Side Request Forgery (SSRF) vulnerability exists in the PowerPack Addons for Elementor: Widgets, Form Styler and Templates WordPress plugin before version 3.1.3. This flaw allows users with contributor role or higher to supply a URL that is not validated before the plugin makes a server-side HTTP request. Exploitation could enable attackers to access internal or loopback network resources and read the responses.

Impact

Users with contributor role and above can exploit this vulnerability to perform SSRF attacks, potentially accessing internal network resources or loopback interfaces that are normally inaccessible externally. This could lead to unauthorized information disclosure from internal systems. There is no indication of active exploitation in the wild.

Summary

The PowerPack Addons for Elementor WordPress plugin versions from 2.10.0 up to but not including 3.1.3 contain a Server-Side Request Forgery vulnerability (CWE-918). The plugin fails to validate user-supplied URLs before using them in server-side HTTP requests. Users with contributor or higher privileges can exploit this to make the server perform HTTP requests to internal or loopback addresses and retrieve the responses, potentially exposing sensitive internal resources. The vulnerability is fixed in version 3.1.3.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/ac6405e6-9a1e-4ad6-bfd7-e672030a31c1/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 06:28 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats