CVE-2026-102244: MODSetter SurfSense Document Export Feature editor_routes.py server-side request forgery
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by VulDB, published 2026-09-29).
Weakness: Server-Side Request Forgery
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality low, integrity none, availability none. 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
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Also known as: EUVD-2026-88618, GHSA-m6qw-8q66-9vp2
VEDAS cluster: VEDAS:DILIGENTDEWAN
Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (3)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-102244.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-102244.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-102244.rules
Vulnerability databases and vendor advisories (3)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-88618
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-m6qw-8q66-9vp2
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-102244
3 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.985
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| MODSetter SurfSense | version 0.0.1 version 0.0.2 version 0.0.3 version 0.0.4 version 0.0.5 version 0.0.6 version 0.0.7 version 0.0.8 and 28 more ranges | 0.0.36.3 is not affected |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Vendor guidance:
- https://github.com/MODSetter/SurfSense/commit/2faff7b3823322a9cb6797973e6caf089386c354 (patch)
- https://github.com/MODSetter/SurfSense/releases/tag/0.0.36.3 (patch)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-102244 SurfSense - Server-Side Request Forgery via note export embedded resource. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-102244 SurfSense - Server-Side Request Forgery via note export embedded resource"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/notes"; nocase; fast_pattern; http.request_body; content:"source_markdown"; nocase; pcre:"/\x5d\x28\s*(?:file|gopher|dict|ftp)\x3a\x2f\x2f|\x5d\x28\s*https?\x3a\x2f\x2f(?:127\.|0\.0\.0\.0|localhost|169\.254\.169\.254|10\.|192\.168\.|172\.(?:1[6-9]|2[0-9]|3[01])\.|\x5b)/i"; classtype:web-application-attack; reference:cve,CVE-2026-102244; reference:url,https://www.exploit.observer/?keyword=CVE-2026-102244&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=surfsense&match=exact; sid:1095205; rev:1;)
CVE-2026-102244.rules on GitHub
References
Vendor advisories and patches
- https://github.com/MODSetter/SurfSense/commit/2faff7b3823322a9cb6797973e6caf089386c354 (patch)
- https://github.com/MODSetter/SurfSense/releases/tag/0.0.36.3 (patch)
Exploits and technical analysis
- CVE-2026-102244 | CVE Analysis and Report (third-party-advisory)
- Submit #933330 | MODSetter SurfSense <=0.0.36 Server-Side Request Forgery (third-party-advisory)
- https://gist.github.com/DReazer/57126e711507324a547edde96c62c218 (exploit)
Other references
- VDB-411142 | MODSetter SurfSense Document Export Feature editor_routes.py server-side request forgery (vdb-entry)
- VDB-411142 | CTI Indicators (IOB, IOC, IOA) (signature, permissions-required)
- https://github.com/MODSetter/SurfSense/ (product)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.