Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-118691medium6.3

xianyu-auto-reply-fix through 2.0.7 Unauthenticated Message Sending via /send-message

Impact

xianyu-auto-reply-fix through 2.0.7 has a missing authorization vulnerability, allowing unauthenticated attackers to send messages from other users' accounts. Attackers can use a publicly known default API secret and another user's cookie_id to send arbitrary messages. The weakness is due to initialization with an insecure default.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

GuDong2003 · VulnCheck

xianyu-auto-reply-fix

1 range

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → through 2.0.7

semver versions

unaffected

unknown

Other versions: unaffected

Original source description

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.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-118691

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-1188 ↗

Initialization of a Resource with an Insecure Default

VulnCheck

Related →
Contributing organizations · 1
VulnCheck

Assigning organization

2026-10-28

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

6 sources