Skip to main content
VulnerabilityPublished

CVE-2026-118691: GuDong2003 xianyu-auto-reply-fix · Insecure Default

Affects GuDong2003 xianyu-auto-reply-fixSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium.

Data as of 28 Oct 2026, 21:42 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GuDong2003xianyu-auto-reply-fixAffected
  • <=2.0.7
Fixed in–
GitHubgudong2003/xianyu-auto-reply-fixpkg:github/gudong2003/xianyu-auto-reply-fixOther threatsAffected
  • <=2.0.7
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since the vulnerability involves default API secrets and missing authorization, immediate mitigation should include changing or invalidating default API keys and implementing proper authorization checks on the POST /send-message endpoint. Monitor vendor advisories for official patches or updates.

Description

CVE-2026-118691 is a vulnerability in GuDong2003's xianyu-auto-reply-fix up to version 2.0.7. It involves a missing authorization check in the POST /send-message endpoint, allowing unauthenticated attackers to send messages on behalf of other users by exploiting publicly known default API secrets. Attackers can use a hard-coded api_key along with another user's cookie_id and arbitrary message parameters to send unauthorized messages.

References

Community reviews

Loading reviews…