{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-5091 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2010-5091 yet. Limit exposure of the affected software until one is available.","what":"CVE-2010-5091 is a medium-severity vulnerability in Silverstripe Silverstripe, published on 26 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2010-5091 and fix it if it is affected.\n\nWhat it is: CVE-2010-5091 is a medium-severity vulnerability in Silverstripe Silverstripe, published on 26 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2010-5091 in the wild and no public exploit code.\n\nAffected product: Silverstripe Silverstripe. 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-5091/ (Markdown: https://insights.sbomify.com/CVE-2010-5091/index.md)","id":"CVE-2010-5091","markdown":"https://insights.sbomify.com/CVE-2010-5091/index.md","name":"CVE-2010-5091","record":{"aliases":["GHSA-mrv2-38v6-5385"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SilverStripe CMS","requires_auth":"low_privilege","summary":"Authenticated CMS authors can execute arbitrary PHP code by manipulating uploaded file extensions in SilverStripe.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"silverstripe","vendor":"silverstripe"}],"cvss":{"score":6,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The setName function in filesystem/File.php in SilverStripe 2.3.x before 2.3.8 and 2.4.x before 2.4.1 allows remote authenticated users with CMS author privileges to execute arbitrary PHP code by changing the extension of an uploaded file.","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":"File upload in n/a","id":"CVE-2010-5091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"silverstripe:silverstripe","products":["silverstripe:silverstripe"],"type":"file_upload","year":"2010"},"n_packages":0,"n_references":8,"next":{"headline":"Information disclosure in n/a","id":"CVE-2010-5092"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2010-5090"},"products":["n/a"],"published":"2012-08-26","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2007-2321","kev_date_added":null,"published":"2007-04-27"},{"cvss_score":9.8,"headline":"Missing warning can lead to unauthenticated admin access in SilverStripe","id":"CVE-2019-12204","kev_date_added":null,"published":"2019-09-25"},{"cvss_score":9.8,"headline":"Silverstripe Framework SQLi Vulnerability","id":"CVE-2019-5715","kev_date_added":null,"published":"2019-04-11"},{"cvss_score":8.8,"headline":"Silverstripe CSRF Protection Bypass via GraphQL","id":"CVE-2019-12437","kev_date_added":null,"published":"2020-02-19"},{"cvss_score":7.5,"headline":"Silverstripe CMS information disclosure","id":"CVE-2020-6164","kev_date_added":null,"published":"2020-07-15"},{"cvss_score":7.5,"headline":"SilverStripe Folders migrated from 3.x may be unsafe to upload to","id":"CVE-2020-9280","kev_date_added":null,"published":"2020-04-15"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2011-4960","kev_date_added":null,"published":"2012-09-17"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Authenticated CMS authors can execute arbitrary PHP code by manipulating uploaded file extensions in SilverStripe.","url":"https://insights.sbomify.com/CVE-2010-5091/"}