# CVE-2026-127140: Server-Side Request Forgery in pretix Widget WordPress plugin


- **Severity:** Low 3.8 (`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:U`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-7fff-j98j-jpqx

## What is CVE-2026-127140?

CVE-2026-127140 is a low-severity vulnerability in pretix Widget Wordpress Plugin, published on 17 Nov 2026. 

### Official description

Our WordPress plugin for the pretix Widget performs HTTP calls to pre-fetch CSS and JS files into a local cache and stores them publicly on the WordPress instance. These HTTP calls are made with wp_remote_get, not wp_safe_remote_get, and therefore allow SSRF with body extraction. Exploiting this requires sufficient WordPress permissions to create or modify pages.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-127140?


## How do I fix CVE-2026-127140?

No fix has been published for CVE-2026-127140 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-127140 being exploited?

There is no known exploitation of CVE-2026-127140 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127140 and fix it if it is affected.

What it is: CVE-2026-127140 is a low-severity vulnerability in pretix Widget Wordpress Plugin, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127140 in the wild and no public exploit code.

Affected product: pretix Widget Wordpress Plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127140/ (Markdown: https://insights.sbomify.com/CVE-2026-127140/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127140
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127140
- OSV: https://osv.dev/vulnerability/CVE-2026-127140

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127140/
Summaries are generated and may contain mistakes; the official description above is the record.
