CVE-2026-22663: prompts.chat authorization bypass in API endpoints and metadata generation

CVE-2026-22663 · Severity: high · CVSS 7.5 · Published 2026-04-03

prompts.chat, a platform for sharing and managing AI prompts, contained a security flaw that allowed unauthorized users to view private content. Attackers could bypass privacy settings to access sensitive prompt history, change requests, and internal metadata that should have been restricted to owners and administrators. This could lead to the exposure of proprietary or confidential AI instructions and user-submitted examples.

Technologies: F Awesome ChatGPT Prompts, Fka Prompts.Chat. Vendors: F, Fka.

Quick answers

Is CVE-2026-22663 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-22663 being exploited in the wild.
How severe is CVE-2026-22663?
High severity, with a CVSS score of 7.5, published 3 April 2026.
Which products and versions are affected?
fka prompts.chat prior to commit 7b81836.
Is there a fix for CVE-2026-22663?
A patch was published on 2026-03-25: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-22663 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-22663?
Check whether you run F Awesome ChatGPT Prompts or Fka Prompts.Chat. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability stems from a missing 'isPrivate' check across several API endpoints and the metadata generation logic in prompts.chat. Specifically, endpoints for version history, change requests, examples, and voting failed to verify if a prompt was marked as private before returning data. An unauthenticated remote attacker could exploit these omissions to retrieve sensitive information, including prompt content, version history, and user metadata exposed via HTML meta tags. The issue was addressed in commit 7b81836 by implementing a centralized 'checkPromptAccess' guard that enforces privacy logic based on the prompt's status and the user's session.

Affected products

  • fka prompts.chat prior to commit 7b81836

Timeline

  • 2026-03-25: patched: Fix committed to repository
  • 2026-04-03: disclosed: Initial advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.