{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-118691 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-118691 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-118691 is a medium-severity vulnerability in GuDong2003 xianyu-auto-reply-fix, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-118691 and fix it if it is affected.\n\nWhat it is: CVE-2026-118691 is a medium-severity vulnerability in GuDong2003 xianyu-auto-reply-fix, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-118691 in the wild and no public exploit code.\n\nAffected product: GuDong2003 xianyu-auto-reply-fix. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-118691/ (Markdown: https://insights.sbomify.com/CVE-2026-118691/index.md)","id":"CVE-2026-118691","markdown":"https://insights.sbomify.com/CVE-2026-118691/index.md","name":"CVE-2026-118691","record":{"aliases":["GHSA-8xg3-rxxw-rm99"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"xianyu-auto-reply-fix through 2.0.7 Unauthenticated Message Sending via /send-message","id":"CVE-2026-118691","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"CherryTree through 1.7.2 OS Command Injection via Custom Web Link Action","id":"CVE-2026-118692"},"packages":[],"prev":{"headline":"Signal K Server before 2.33.0 Missing Authentication via /skServer/ziplogs","id":"CVE-2026-118690"},"products":["xianyu-auto-reply-fix"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["GuDong2003"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-118691/"}