{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51949 exists.","fix":"No fix has been published for CVE-2023-51949 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-51949 is a high-severity vulnerability in n/a, published on 12 Jan 2024. 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-2023-51949 and fix it if it is affected.\n\nWhat it is: CVE-2023-51949 is a high-severity vulnerability in n/a, published on 12 Jan 2024. 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-2023-51949 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-2023-51949/ (Markdown: https://insights.sbomify.com/CVE-2023-51949/index.md)","id":"CVE-2023-51949","markdown":"https://insights.sbomify.com/CVE-2023-51949/index.md","name":"CVE-2023-51949","record":{"aliases":["GHSA-3836-7r6q-99c9"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Verydows web application","requires_auth":"none","summary":"An attacker can perform unauthorized actions on behalf of a logged-in user in the Verydows backend role controller via CSRF.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"verydows","vendor":"verydows"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Verydows v2.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /protected/controller/backend/role_controller","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-2023-51949","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2023-51951"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2023-51948"},"products":["n/a"],"published":"2024-01-12","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-23363","kev_date_added":null,"published":"2023-05-09"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-7737","kev_date_added":null,"published":"2019-02-11"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2022-28058","kev_date_added":null,"published":"2022-04-26"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2022-28059","kev_date_added":null,"published":"2022-04-26"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-8363","kev_date_added":null,"published":"2019-02-16"},{"cvss_score":6.1,"headline":"Verydows 2.0 has XSS via the index.php?m=api\u0026c=stats\u0026a=count referrer parameter.","id":"CVE-2019-7753","kev_date_added":null,"published":"2019-02-12"}],"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-06-17","vendors":["n/a"]},"summary":"An attacker can perform unauthorized actions on behalf of a logged-in user in the Verydows backend role controller via CSRF.","url":"https://insights.sbomify.com/CVE-2023-51949/"}