{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15753 exists.","fix":"No fix has been published for CVE-2026-15753 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15753 is a medium-severity missing authorization vulnerability in zhinianboke xianyu-auto-reply, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-15753 and fix it if it is affected.\n\nWhat it is: CVE-2026-15753 is a medium-severity missing authorization vulnerability in zhinianboke xianyu-auto-reply, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15753 exists.\n\nAffected product: zhinianboke xianyu-auto-reply. 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-15753/ (Markdown: https://insights.sbomify.com/CVE-2026-15753/index.md)","id":"CVE-2026-15753","markdown":"https://insights.sbomify.com/CVE-2026-15753/index.md","name":"CVE-2026-15753","record":{"aliases":["GHSA-3rf8-mgfc-9vfp"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Xianyu auto-reply bot","requires_auth":"low_privilege","summary":"Attackers can bypass server-side permission checks to approve payment withdrawals, leading to unauthorized financial transactions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-650","name":"Trusting HTTP Permission Methods on the Server Side"}],"description":"A vulnerability was determined in zhinianboke xianyu-auto-reply on Server. Affected by this vulnerability is an unknown functionality of the file /api/v1/payment/withdraw/review?action=approve. Executing a manipulation can lead to trusting http permission methods on the server side. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized. This patch is called 19fc3282a1bb78a05c34945c088525d20e081cbd. It is best practice to apply a patch to resolve this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"zhinianboke xianyu-auto-reply review approve trusting http permission methods on the server side","id":"CVE-2026-15753","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Missing per-channel team-scope check in ABAC access control policy unassign allows cross-team policy removal","id":"CVE-2026-15754"},"packages":[],"prev":{"headline":"zhinianboke xianyu-auto-reply Backend User Endpoint users authorization","id":"CVE-2026-15752"},"products":["xianyu-auto-reply"],"published":"2026-07-14","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["zhinianboke"]},"summary":"Attackers can bypass server-side permission checks to approve payment withdrawals, leading to unauthorized financial transactions.","url":"https://insights.sbomify.com/CVE-2026-15753/"}