# CVE-2026-102244: MODSetter SurfSense Document Export Feature editor_routes.py server-side request forgery

> Remote attackers can exploit a server-side request forgery flaw in the document export feature to access internal resources or bypass security controls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-m6qw-8q66-9vp2

## What is CVE-2026-102244?

CVE-2026-102244 is a medium-severity server-side request forgery vulnerability in MODSetter SurfSense, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in MODSetter SurfSense up to 0.0.36. Impacted is an unknown function of the file surfsense_backend/app/routes/editor_routes.py of the component Document Export Feature. Performing a manipulation results in server-side request forgery. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 0.0.36.3 is recommended to address this issue. The patch is named 2faff7b3823322a9cb6797973e6caf089386c354. The affected component should be upgraded.

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

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


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

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

## Is CVE-2026-102244 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102244 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102244 is a medium-severity server-side request forgery vulnerability in MODSetter SurfSense, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102244 exists.

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

## Sources

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

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