CVE-2026-22663 | prompts.chat API Endpoint authorization
VulDBArchived Apr 04, 2026✓ Full text saved
A vulnerability marked as problematic has been reported in prompts.chat . Affected by this issue is some unknown functionality of the component API Endpoint . Performing a manipulation results in missing authorization. This vulnerability is identified as CVE-2026-22663 . The attack can be initiated remotely. There is not any exploit available. It is recommended to apply a patch to fix this issue.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355192 · CVE-2026-22663 · GCVE-0-2026-22663
PROMPTS.CHAT API ENDPOINT AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
6.3 $0-$5k 0.67+
Summaryinfo
A vulnerability described as problematic has been identified in prompts.chat. This affects an unknown part of the component API Endpoint. Executing a manipulation can lead to authorization. This vulnerability is tracked as CVE-2026-22663. The attack can be launched remotely. No exploit exists. Applying a patch is advised to resolve this issue.
Detailsinfo
A vulnerability was found in prompts.chat (unknown version). It has been declared as problematic. This vulnerability affects an unknown code block of the component API Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality. CVE summarizes:
prompts.chat prior to commit 7b81836 contains multiple authorization bypass vulnerabilities due to missing isPrivate checks across API endpoints and page metadata generation that allow unauthorized users to access sensitive data associated with private prompts. Attackers can exploit these missing authorization checks to retrieve private prompt version history, change requests, examples, current content, and metadata including titles and descriptions exposed via HTML meta tags.
The weakness was disclosed by mdisec. The advisory is shared for download at github.com. This vulnerability was named CVE-2026-22663 since 01/08/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.
Applying the patch 7b81836b214f2796aaf37ded2944eadc978afd35 is able to eliminate this problem.
Productinfo
Type
Chat Software
Name
prompts.chat
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (VulnCheck): 🔒
CVSSv2info
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: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Patch
Status: 🔍
0-Day Time: 🔒
Patch: 7b81836b214f2796aaf37ded2944eadc978afd35
Timelineinfo
01/08/2026 CVE reserved
04/03/2026 +84 days Advisory disclosed
04/03/2026 +0 days VulDB entry created
04/03/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: github.com
Researcher: mdisec
Status: Confirmed
CVE: CVE-2026-22663 (🔒)
GCVE (CVE): GCVE-0-2026-22663
GCVE (VulDB): GCVE-100-355192
Entryinfo
Created: 04/03/2026 23:21
Changes: 04/03/2026 23:21 (75)
Complete: 🔍
Cache ID: 99:074:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸