Read the docs

Missing authorization in xianyu-auto-reply-fix allows message sending

Priority MEDIUM 61CWE-1188Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

xianyu-auto-reply-fix through 2.0.7 contains a missing authorization check in the POST /send-message endpoint. An unauthenticated remote attacker can send Xianyu messages from another user's account to that merchant's buyers by using the publicly known default API secret. The flaw stems from an insecure default configuration (CWE-1188).

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Description from the CNA

xianyu-auto-reply-fix through 2.0.7 contains a missing authorization vulnerability in the POST /send-message endpoint that allows unauthenticated attackers to send messages from other users' accounts using publicly known default API secrets. Attackers can supply the hard-coded api_key and another user's cookie_id, plus chosen chat_id, to_user_id and message values, to send arbitrary Xianyu messages to buyers from that merchant account.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00316 24th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
GuDong2003xianyu-auto-reply-fixup to 2.0.7—No fix listedCNA
  • xianyu-auto-reply-fix VendorGuDong2003 Affected up to 2.0.7 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for xianyu-auto-reply-fix.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Timeline

  1. 2026-10-28 Threatist record created from CVE-2026-118691
  2. 2026-10-29 Alias added: GHSA-8xg3-rxxw-rm99
  3. 2026-10-30 Priority changed: MEDIUM → LOW
  4. 2026-11-03 CISA SSVC decision points changed
  5. 2026-11-03 Priority changed: LOW → MEDIUM

References

Sources