Loading vulnerability…
FastGPT Community Edition versions 4.10.0 through 4.14.0 contain an unauthenticated NoSQL injection vulnerability in the chat-history retrieval API. Crafted JSON values containing NoSQL operators can be injected into query processing and bypass authorization checks intended to restrict access to a caller's own chat histories.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
The repository contains two bilingual Markdown advisories and one Python 3 proof-of-concept, poc.py. The script accepts an operator-supplied FastGPT base URL, constructs POST <target>/api/core/chat/getHistories, and uses urllib.request with browser-like headers, an Origin and Referer derived from the supplied target, and a locale cookie. Its JSON body places MongoDB $ne operators in shareId and outLinkUid, attempting to bypass FastGPT Community Edition outLink authorization through NoSQL injection. It parses the JSON response and treats data.total greater than zero as successful exploitation, printing the count and first chat-history title. The stated impact is unauthenticated disclosure of chat-history titles across users. This is a functional but narrow, hardcoded operational PoC rather than a framework module or a destructive payload.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.