{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54851 exists.","fix":"No fix has been published for CVE-2024-54851 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-54851 is a high-severity vulnerability in n/a, published on 29 Jan 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-2024-54851 and fix it if it is affected.\n\nWhat it is: CVE-2024-54851 is a high-severity vulnerability in n/a, published on 29 Jan 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-2024-54851 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-2024-54851/ (Markdown: https://insights.sbomify.com/CVE-2024-54851/index.md)","id":"CVE-2024-54851","markdown":"https://insights.sbomify.com/CVE-2024-54851/index.md","name":"CVE-2024-54851","record":{"aliases":["GHSA-7xmr-c34w-p9w7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Teedy document management","requires_auth":"none","summary":"Attackers can perform unauthorized actions on behalf of authenticated users due to missing CSRF protection in Teedy.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"teedy","vendor":"sismics"}],"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":"Teedy \u003c= 1.12 is vulnerable to Cross Site Request Forgery (CSRF), due to the lack of CSRF protection.","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-2024-54851","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2024-54852"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2024-54849"},"products":["n/a"],"published":"2025-01-29","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2024-54852","kev_date_added":null,"published":"2025-01-29"},{"cvss_score":9.6,"headline":"Teedy - Reflected Cross-Site Scripting (XSS) in the Search Functionality","id":"CVE-2022-22114","kev_date_added":null,"published":"2022-01-10"},{"cvss_score":9,"headline":"Teedy - Stored Cross-Site Scripting (XSS) in Tag Name","id":"CVE-2022-22115","kev_date_added":null,"published":"2022-01-10"},{"cvss_score":8.4,"headline":"Cross-site scripting in n/a","id":"CVE-2024-46278","kev_date_added":null,"published":"2024-10-07"},{"cvss_score":7.5,"headline":"Cross-site request forgery in Teedy","id":"CVE-2025-22963","kev_date_added":null,"published":"2025-01-13"},{"cvss_score":5.7,"headline":"Teedy v1.11 - Stored cross-site scripting (XSS)","id":"CVE-2023-4892","kev_date_added":null,"published":"2023-09-25"}],"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":"total"},"state":"PUBLISHED","updated":"2025-01-30","vendors":["n/a"]},"summary":"Attackers can perform unauthorized actions on behalf of authenticated users due to missing CSRF protection in Teedy.","url":"https://insights.sbomify.com/CVE-2024-54851/"}