CVE-2026-68929: FastGPT: Unauthenticated WeChat channel hijack and denial of service via shareId-only authorization
FastGPT is an open-source LLM platform for building AI applications on a knowledge base. In versions prior to 4.15.2, the WeChat (iLink) share-channel endpoints authorize requests using only the public shareId, with no authenticated identity or team-ownership check. As a result, an unauthenticated attacker who knows a victim team's shareId can take that team's WeChat bot offline or hijack the channel to their own bot: the logout endpoint is gated only by an existence check yet wipes the outLink's stored WeChat token, and the QR-code status endpoint performs no authorization at all and writes attacker-supplied bot credentials into the outLink identified by shareId. By generating a QR for a victim shareId, scanning it with their own WeChat, and calling the status endpoint, an attacker binds the victim team's app to the attacker's bot, exposing the app's private responses, displacing the legitimate binding, and consuming the victim's resources. The shareId is exposed in every shared chat URL, iframe, and embed, so it is not a secret. This issue is fixed in version 4.15.2.
Security readout for executives and security teams
Plain-English summary
FastGPT’s WeChat sharing feature treated a public share identifier like a password. An unauthenticated attacker who obtains that identifier from a shared link or embed could disconnect the legitimate bot or replace it with their own, potentially exposing private app responses and consuming victim resources.
Executive priority
Treat as an immediate remediation priority wherever affected WeChat sharing is enabled. Channel hijacking could expose private AI responses and disrupt customer-facing bots without authentication. Quickly inventory deployments, upgrade affected instances, and examine existing bindings for compromise indicators.
Technical view
Affected WeChat iLink endpoints lack authentication and team-ownership authorization. The logout endpoint can erase the stored WeChat token, while the QR-status endpoint can write attacker-controlled bot credentials to the record selected by shareId. FastGPT 4.15.2 fixes the issue.
Likely exposure
Exposure is limited to FastGPT versions 4.14.10–4.14.28 and 4.15.0–4.15.1 using WeChat iLink share channels. Risk is substantial because shareId appears in shared chat URLs, iframes, and embeds and is explicitly not a secret.
Exploitation context
The CVSS 4.0 score is 9.3, reflecting remote, low-complexity exploitation without privileges or victim interaction and potentially high confidentiality, integrity, and availability impact. The supplied record is not in KEV, and the sources provide no evidence of active exploitation.
Researcher notes
The core weakness combines missing authentication and missing authorization, mapped to CWE-306 and CWE-862. The public shareId directly selects the victim’s outLink record. Evidence supports confidentiality, integrity, and availability impact, but the supplied sources do not establish exploitation in the wild.
Mitigation direction
Upgrade affected FastGPT deployments to version 4.15.2 or later.
Until upgraded, disable affected WeChat iLink sharing or restrict access to its endpoints.
After upgrading, verify every WeChat channel remains bound to the intended bot.
Reset suspicious bindings and credentials according to current vendor guidance.
Validation and detection
Inventory FastGPT versions and compare them with both documented affected ranges.
Identify deployments and teams using WeChat iLink share channels.
Review channel records for unexplained logout, token removal, or bot-binding changes.
Confirm upgraded deployments run FastGPT 4.15.2 or later.
Verify affected endpoints enforce authentication and team-ownership authorization after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.