BigSweetPotatoStudio HyperChat up to 2.0.0-alpha.63 AI Proxy Middleware aiProxyMiddleware.mts fetch baseurl server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in BigSweetPotatoStudio HyperChat up to 2.0.0-alpha.63. This affects the function fetch of the file packages/core/src/http/aiProxyMiddleware.mts of the component AI Proxy Middleware. Performing a manipulation of the argument baseurl results in server-side request forgery.
This vulnerability was named CVE-2026-7223. The attack may be initiated remotely. In addition, an exploit is available.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability, which was classified as critical, was found in BigSweetPotatoStudio HyperChat up to 2.0.0-alpha.63. This affects the function fetch of the file packages/core/src/http/aiProxyMiddleware.mts of the component AI Proxy Middleware. The manipulation of the argument baseurl with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-7223. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
- 2.0.0-alpha.0
- 2.0.0-alpha.1
- 2.0.0-alpha.2
- 2.0.0-alpha.3
- 2.0.0-alpha.4
- 2.0.0-alpha.5
- 2.0.0-alpha.6
- 2.0.0-alpha.7
- 2.0.0-alpha.8
- 2.0.0-alpha.9
- 2.0.0-alpha.10
- 2.0.0-alpha.11
- 2.0.0-alpha.12
- 2.0.0-alpha.13
- 2.0.0-alpha.14
- 2.0.0-alpha.15
- 2.0.0-alpha.16
- 2.0.0-alpha.17
- 2.0.0-alpha.18
- 2.0.0-alpha.19
- 2.0.0-alpha.20
- 2.0.0-alpha.21
- 2.0.0-alpha.22
- 2.0.0-alpha.23
- 2.0.0-alpha.24
- 2.0.0-alpha.25
- 2.0.0-alpha.26
- 2.0.0-alpha.27
- 2.0.0-alpha.28
- 2.0.0-alpha.29
- 2.0.0-alpha.30
- 2.0.0-alpha.31
- 2.0.0-alpha.32
- 2.0.0-alpha.33
- 2.0.0-alpha.34
- 2.0.0-alpha.35
- 2.0.0-alpha.36
- 2.0.0-alpha.37
- 2.0.0-alpha.38
- 2.0.0-alpha.39
- 2.0.0-alpha.40
- 2.0.0-alpha.41
- 2.0.0-alpha.42
- 2.0.0-alpha.43
- 2.0.0-alpha.44
- 2.0.0-alpha.45
- 2.0.0-alpha.46
- 2.0.0-alpha.47
- 2.0.0-alpha.48
- 2.0.0-alpha.49
- 2.0.0-alpha.50
- 2.0.0-alpha.51
- 2.0.0-alpha.52
- 2.0.0-alpha.53
- 2.0.0-alpha.54
- 2.0.0-alpha.55
- 2.0.0-alpha.56
- 2.0.0-alpha.57
- 2.0.0-alpha.58
- 2.0.0-alpha.59
- 2.0.0-alpha.60
- 2.0.0-alpha.61
- 2.0.0-alpha.62
- 2.0.0-alpha.63
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
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
04/27/2026 Advisory disclosed04/27/2026 VulDB entry created
04/27/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 142
Status: Not defined
CVE: CVE-2026-7223 (🔒)
GCVE (CVE): GCVE-0-2026-7223
GCVE (VulDB): GCVE-100-359823
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 04/27/2026 17:43Changes: 04/27/2026 17:43 (60)
Complete: 🔍
Submitter: BruceJin
Cache ID: 216::103
Submit
Accepted
- Submit #802265: BigSweetPotatoStudio HyperChat 2.0.0-alpha.63 Server-Side Request Forgery (by BruceJin)
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.