{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63711 exists.","fix":"No fix has been published for CVE-2025-63711 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63711 is a high-severity vulnerability in n/a, published on 10 Nov 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-63711 and fix it if it is affected.\n\nWhat it is: CVE-2025-63711 is a high-severity vulnerability in n/a, published on 10 Nov 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-63711 exists.\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-63711/ (Markdown: https://insights.sbomify.com/CVE-2025-63711/index.md)","id":"CVE-2025-63711","markdown":"https://insights.sbomify.com/CVE-2025-63711/index.md","name":"CVE-2025-63711","record":{"aliases":["GHSA-qm2h-8p28-f32f"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Client Database Management System","requires_auth":"none","summary":"An attacker can trick an authenticated admin into deleting user accounts via a malicious page due to missing CSRF protections.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"client_database_management_system","vendor":"lerouxyxchire"}],"cvss":{"score":7.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A Cross-Site Request Forgery (CSRF) vulnerability in the SourceCodester Client Database Management System 1.0 allows an attacker to cause an authenticated administrative user to perform user deletion actions without their consent. The application's user deletion endpoint (e.g., superadmin_user_delete.php) accepts POST requests containing a user_id parameter and does not enforce request origin or anti-CSRF tokens. Because the endpoint lacks proper authentication/authorization checks and CSRF protections, a remote attacker can craft a malicious page that triggers deletion when visited by an authenticated admin, resulting in arbitrary removal of user accounts.","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":"Cross-site request forgery in n/a","id":"CVE-2025-63711","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-63712"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-63710"},"products":["n/a"],"published":"2025-11-10","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-46188","kev_date_added":null,"published":"2025-05-09"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-46189","kev_date_added":null,"published":"2025-05-09"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-46190","kev_date_added":null,"published":"2025-05-09"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-46191","kev_date_added":null,"published":"2025-05-09"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-46192","kev_date_added":null,"published":"2025-05-09"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-46193","kev_date_added":null,"published":"2025-05-09"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-10","vendors":["n/a"]},"summary":"An attacker can trick an authenticated admin into deleting user accounts via a malicious page due to missing CSRF protections.","url":"https://insights.sbomify.com/CVE-2025-63711/"}