# CVE-2026-101300: Server-Side Request Forgery in Wegow PDF export

> Authenticated promoters can exploit SSRF in PDF export to force the service to fetch external resources, potentially accessing internal data or bypassing network restrictions.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-4f96-74rp-x9cg

## What is CVE-2026-101300?

CVE-2026-101300 is a high-severity server-side request forgery vulnerability in Wegow, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) reported in the ticket sales chart PDF export functionality of Wegow. According to the report, an authenticated user with a promoter account can manipulate the <svg> parameter of the POST request generated by selecting Download PDF. The content is processed by the export.highcharts.com service, which sends HTTP requests to attacker-controlled external resources and embeds their responses in the generated PDF. The reported behavior allows the export service to be used as an intermediary for these requests.

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

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


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

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

## Is CVE-2026-101300 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101300 is a high-severity server-side request forgery vulnerability in Wegow, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-101300 in the wild and no public exploit code.

Affected product: Wegow. 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-101300/ (Markdown: https://insights.sbomify.com/CVE-2026-101300/index.md)
```

## Sources

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

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