Answer in brief
CVE-2026-14714 records a Medium severity (CVSS 6.5) vulnerability in zhayujie chatgpt-on-wechat CowAgent wx Endpoint common.py verify_server missing authentication. The current sources do not mark it as known exploited. The current feed maps zhayujie/chatgpt-on-wechat CowAgent (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps zhayujie/chatgpt-on-wechat CowAgent (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| zhayujie/chatgpt-on-wechat CowAgentgeneric | 2.1.0 | Not reported |
Published upstream
Jul 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 5, 2026
A weakness has been identified in zhayujie chatgpt-on-wechat CowAgent 2.1.0. This issue affects the function verify_server of the file channel/wechatmp/common.py of the component wx Endpoint. This manipulation of the argument wechatmp_token causes missing authentication. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 2.1.1 is capable of addressing this issue. Patch name: 3d7c68bac6ee74fad63f43cf99e45c62e202ed55. It is suggested to upgrade the affected component. The project confirms: "We've added an explicit non-empty check for wechatmp_token in verify_server() so that the /wx endpoint now fails closed with 403 Forbidden whenever the token is missing or left at the default empty value, instead of relying on a signature check that silently degenerates to a predictable hash."
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-14714 records a Medium severity (CVSS 6.5) vulnerability in zhayujie chatgpt-on-wechat CowAgent wx Endpoint common.py verify_server missing authentication. The current sources do not mark it as known exploited. The current feed maps zhayujie/chatgpt-on-wechat CowAgent (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps zhayujie/chatgpt-on-wechat CowAgent (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| zhayujie/chatgpt-on-wechat CowAgentgeneric | 2.1.0 | Not reported |
Published upstream
Jul 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 5, 2026
A weakness has been identified in zhayujie chatgpt-on-wechat CowAgent 2.1.0. This issue affects the function verify_server of the file channel/wechatmp/common.py of the component wx Endpoint. This manipulation of the argument wechatmp_token causes missing authentication. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 2.1.1 is capable of addressing this issue. Patch name: 3d7c68bac6ee74fad63f43cf99e45c62e202ed55. It is suggested to upgrade the affected component. The project confirms: "We've added an explicit non-empty check for wechatmp_token in verify_server() so that the /wx endpoint now fails closed with 403 Forbidden whenever the token is missing or left at the default empty value, instead of relying on a signature check that silently degenerates to a predictable hash."
Quoted source text, attributed separately from HOL analysis.