prompts.chat Wiro Service inputImageUrl server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in prompts.chat and classified as critical. The impacted element is an unknown function of the component Wiro Service. Performing a manipulation of the argument inputImageUrl results in server-side request forgery. This vulnerability is reported as CVE-2026-22662. The attack is possible to be carried out remotely. No exploit exists. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, was found in prompts.chat (the affected version unknown). This affects an unknown part of the component Wiro Service. The manipulation of the argument inputImageUrl 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. The summary by CVE is:
prompts.chat prior to commit 1464475 contains a blind server-side request forgery vulnerability in the Wiro media generator that allows authenticated users to perform server-side fetches of user-controlled inputImageUrl parameters. Attackers can exploit this vulnerability by sending POST requests to the /api/media-generate endpoint to probe internal networks, access internal services, and exfiltrate data through the upstream Wiro service without receiving direct response bodies.
The weakness was disclosed by mdisec. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-22662 since 01/08/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.
Applying the patch 66de14d3cf3f99489ac9840fad66c7f1ddedb7a8 is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-18823). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (VulnCheck): 🔒
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: 🔒
Status: Not defined
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: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 66de14d3cf3f99489ac9840fad66c7f1ddedb7a8
Timeline
01/08/2026 CVE reserved04/03/2026 Advisory disclosed
04/03/2026 VulDB entry created
04/04/2026 VulDB entry last update
Sources
Advisory: github.comResearcher: mdisec
Status: Confirmed
CVE: CVE-2026-22662 (🔒)
GCVE (CVE): GCVE-0-2026-22662
GCVE (VulDB): GCVE-100-355197
EUVD: 🔒
Entry
Created: 04/03/2026 23:23Updated: 04/04/2026 05:09
Changes: 04/03/2026 23:23 (77), 04/04/2026 05:09 (1)
Complete: 🔍
Cache ID: 216:23D:103
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.