MODSetter SurfSense up to 2.0.3 MCP Connector Integration test command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 1.99 |
Summary
A vulnerability has been found in MODSetter SurfSense up to 2.0.3 and classified as critical. Impacted is an unknown function of the file /api/search-source/connectors/mcp/test of the component MCP Connector Integration. Performing a manipulation results in command injection. This vulnerability is identified as CVE-2026-102243. The attack can be initiated remotely. Additionally, an exploit exists. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability, which was classified as critical, was found in MODSetter SurfSense up to 2.0.3. This affects an unknown part of the file /api/search-source/connectors/mcp/test of the component MCP Connector Integration. The manipulation with an unknown input leads to a command injection vulnerability. CWE is classifying the issue as CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at gist.github.com. This vulnerability is uniquely identified as CVE-2026-102243. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1202 for this issue.
The exploit is shared for download at gist.github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.4
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Command injectionCWE: CWE-77 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/28/2026 Advisory disclosed09/28/2026 VulDB entry created
09/28/2026 VulDB entry last update
Sources
Advisory: gist.github.comStatus: Confirmed
CVE: CVE-2026-102243 (🔒)
GCVE (CVE): GCVE-0-2026-102243
GCVE (VulDB): GCVE-100-411141
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/28/2026 20:51Changes: 09/28/2026 20:51 (56)
Complete: 🔍
Submitter: Snkn0w
Cache ID: 216::103
Submit
Accepted
- Submit #933323: MODSetter SurfSense <=0.0.36 Command Injection (by Snkn0w)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.