{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-25769 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-25769 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25769 is a high-severity vulnerability in n/a, published on 21 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-25769 and fix it if it is affected.\n\nWhat it is: CVE-2025-25769 is a high-severity vulnerability in n/a, published on 21 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-25769 in the wild and no public exploit code.\n\nAffected product: n/a. 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-25769/ (Markdown: https://insights.sbomify.com/CVE-2025-25769/index.md)","id":"CVE-2025-25769","markdown":"https://insights.sbomify.com/CVE-2025-25769/index.md","name":"CVE-2025-25769","record":{"aliases":["GHSA-4mp4-36x3-25jw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Wangmarket e-commerce","requires_auth":"low_privilege","summary":"Attackers can perform unauthorized actions on behalf of authenticated users in Wangmarket via CSRF in the user controller.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wangmarket","vendor":"wang.market"}],"cvss":{"score":8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Wangmarket v4.10 to v5.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /controller/UserController.java.","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":"Cross-site request forgery in n/a","id":"CVE-2025-25769","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-25770"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2025-25768"},"products":["n/a"],"published":"2025-02-21","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-26813","kev_date_added":null,"published":"2023-04-28"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-25770","kev_date_added":null,"published":"2025-02-21"},{"cvss_score":5.1,"headline":"xnx3 wangmarket XML File uploadImage.do uploadImage unrestricted upload","id":"CVE-2025-15415","kev_date_added":null,"published":"2026-01-01"},{"cvss_score":4.8,"headline":"xnx3 wangmarket System Variables variableSave.do cross site scripting","id":"CVE-2025-15451","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":4.8,"headline":"xnx3 wangmarket Backend Variable Search variableList.do variableList cross site scripting","id":"CVE-2025-15452","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":4.8,"headline":"xnx3 wangmarket Add Global Variable save.do cross site scripting","id":"CVE-2025-15416","kev_date_added":null,"published":"2026-01-01"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-24","vendors":["n/a"]},"summary":"Attackers can perform unauthorized actions on behalf of authenticated users in Wangmarket via CSRF in the user controller.","url":"https://insights.sbomify.com/CVE-2025-25769/"}