{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5521 exists.","fix":"No fix has been published for CVE-2025-5521 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5521 is a medium-severity vulnerability in WuKongOpenSource WukongCRM, published on 3 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-5521 and fix it if it is affected.\n\nWhat it is: CVE-2025-5521 is a medium-severity vulnerability in WuKongOpenSource WukongCRM, published on 3 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5521 exists.\n\nAffected product: WuKongOpenSource WukongCRM. 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-2025-5521/ (Markdown: https://insights.sbomify.com/CVE-2025-5521/index.md)","id":"CVE-2025-5521","markdown":"https://insights.sbomify.com/CVE-2025-5521/index.md","name":"CVE-2025-5521","record":{"aliases":["GHSA-8v33-w22p-qf3q"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WukongCRM","requires_auth":"none","summary":"Attackers can force authenticated users to change their passwords via CSRF, potentially leading to account takeover in WukongCRM.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"wukong_crm","vendor":"5kcrm"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A vulnerability was found in WuKongOpenSource WukongCRM 9.0. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /system/user/updataPassword. The manipulation leads to cross-site request forgery. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"WuKongOpenSource WukongCRM updataPassword cross-site request forgery","id":"CVE-2025-5521","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"jack0240 魏 bskms 蓝天幼儿园管理系统 User Creation addUser improper authorization","id":"CVE-2025-5522"},"packages":[],"prev":{"headline":"Open5GS AMF/MME emm_state_authentication assertion","id":"CVE-2025-5520"},"products":["WukongCRM"],"published":"2025-06-03","related":[{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2024-23052","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":6.5,"headline":"Deserialization in n/a","id":"CVE-2025-60828","kev_date_added":null,"published":"2025-10-08"},{"cvss_score":5.3,"headline":"WuKongOpenSource WukongCRM URL PermissionServiceImpl.java improper authorization","id":"CVE-2026-2141","kev_date_added":null,"published":"2026-02-08"},{"cvss_score":5.3,"headline":"WuKongOpenSource WukongCRM API Response upload information exposure","id":"CVE-2025-8852","kev_date_added":null,"published":"2025-08-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-03","vendors":["WuKongOpenSource"]},"summary":"Attackers can force authenticated users to change their passwords via CSRF, potentially leading to account takeover in WukongCRM.","url":"https://insights.sbomify.com/CVE-2025-5521/"}