CVE-2026-102244
Received Received - Intake

Server-Side Request Forgery in MODSetter SurfSense

Publication date: 2026-09-29

Last updated on: 2026-09-29

Assigner: VulDB

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-29
Last Modified
2026-09-29
Generated
2026-09-29
AI Q&A
2026-09-29
EPSS Evaluated
N/A
NVD
CVE-2026-102244
EUVD
EUVD-2026-88618

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
modsetter surfsense to 0.0.36 (inc)
modsetter surfsense 0.0.36.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Server-Side Request Forgery (SSRF) flaw in MODSetter SurfSense up to version 0.0.36. It exists in the Document Export Feature, specifically in the file surfsense_backend/app/routes/editor_routes.py. An attacker can manipulate user-controlled Markdown during HTML export via Pandoc to craft malicious requests. This allows fetching arbitrary files from the server or internal systems using file:// URIs or accessing restricted HTTP/HTTPS services.

Detection Guidance

To detect this SSRF vulnerability in SurfSense, check for unauthorized file:// or internal HTTP requests in server logs during document export. Look for Base64-encoded data URIs in HTML exports. Verify if Pandoc's --embed-resources flag is used without URI validation. Monitor for unusual outbound requests from the SurfSense backend process.

Impact Analysis

If exploited, this vulnerability could allow an attacker to read sensitive files on the server, such as /etc/passwd or /etc/hostname. It may also enable access to internal services or restricted networks reachable from the server. The impact requires authentication but can be executed by any registered user with note creation and export permissions, which are default in self-hosted setups.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating privacy and security requirements under GDPR and HIPAA. GDPR requires protecting personal data, while HIPAA mandates safeguarding protected health information. A breach via SSRF could result in non-compliance, legal penalties, and loss of trust due to unauthorized data exposure.

Mitigation Strategies

Immediately upgrade SurfSense to version 0.0.36.3 or later. Disable PDF export functionality if present. Restrict Pandoc's --embed-resources flag to only allow http/https URIs. Block file:// and other non-HTTP schemes in Markdown processing. Restrict export features to authenticated users only and limit note creation permissions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-102244. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart