{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-5260 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-5260 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-5260 is a medium-severity path traversal vulnerability in n/a, published on 7 Sep 2012. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2010-5260 and fix it if it is affected.\n\nWhat it is: CVE-2010-5260 is a medium-severity path traversal vulnerability in n/a, published on 7 Sep 2012. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2010-5260 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-2010-5260/ (Markdown: https://insights.sbomify.com/CVE-2010-5260/index.md)","id":"CVE-2010-5260","markdown":"https://insights.sbomify.com/CVE-2010-5260/index.md","name":"CVE-2010-5260","record":{"aliases":["GHSA-c6cr-9436-vv5x"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"DVD ripping software","requires_auth":"none","summary":"Local attackers can execute arbitrary code and gain privileges by placing a malicious DLL in the application's working directory.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"argin_all_dvd_ripper","vendor":"agrinsoft"}],"cvss":{"score":6.9,"severity":"medium","source":"nvd","vector":"AV:L/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Untrusted search path vulnerability in Agrin All DVD Ripper 4.0 allows local users to gain privileges via a Trojan horse wnaspi32.dll file in the current working directory, as demonstrated by a directory that contains a .ifo file.  NOTE: some of these details are obtained from third party information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2010-5260","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2010"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2010-5261"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2010-5259"},"products":["n/a"],"published":"2012-09-07","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Local attackers can execute arbitrary code and gain privileges by placing a malicious DLL in the application's working directory.","url":"https://insights.sbomify.com/CVE-2010-5260/"}