Our WordPress plugin for the pretix Widget performs HTTP calls to pre-fetch CSS and JS files into a local cache and
Source GCVE Database
Not known to be exploited · CVSS 3.8 Low : upgrade to 1.1.2 when convenient.
Data as of 17 Nov 2026, 17:04 UTC
Thin evidence
One scorer or none| CNA (pretix) | CVSS 4.0 | 3.8 |
|---|
- Patch
- Available – fixed in 1.1.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 17 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 16 Nov 2026.
What to do
Upgrade pretix Widget Wordpress Plugin and pretix-widget to 1.1.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pretix Widget Wordpress Pluginpretix-widget | Affected
| Fixed in
|
GitHubpretix-widgetpkg:github/pretix-widgetOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since the plugin uses wp_remote_get instead of wp_safe_remote_get, updating the plugin to use safe HTTP request functions or applying vendor-provided patches (if any) is recommended. If you cannot patch yet, restrict WordPress user permissions to prevent unauthorized page creation or modification by untrusted users. Monitor vendor advisories for official remediation guidance.
Description
The WordPress plugin for the pretix Widget performs HTTP requests to pre-fetch CSS and JS files into a local cache stored publicly on the WordPress instance. These requests use wp_remote_get instead of the safer wp_safe_remote_get, enabling Server-Side Request Forgery (SSRF) with body extraction. Exploitation requires sufficient WordPress permissions to create or modify pages.