{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-6568 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-6568 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-6568 is a high-severity vulnerability in n/a, published on 14 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-6568 and fix it if it is affected.\n\nWhat it is: CVE-2015-6568 is a high-severity vulnerability in n/a, published on 14 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-6568 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-2015-6568/ (Markdown: https://insights.sbomify.com/CVE-2015-6568/index.md)","id":"CVE-2015-6568","markdown":"https://insights.sbomify.com/CVE-2015-6568/index.md","name":"CVE-2015-6568","record":{"aliases":["GHSA-x5m3-795f-59g3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Wolf CMS","requires_auth":"low_privilege","summary":"Authenticated users can upload malicious PHP files by renaming extensions, leading to remote code execution on the server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wolf_cms","vendor":"wolfcms"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Wolf CMS before 0.8.3.1 allows unrestricted file rename and PHP Code Execution because admin/plugin/file_manager/browse/ (aka the filemanager) does not prevent a change of a file extension to \".php\" after originally using the parameter \"filename\" for uploading a JPEG image. Exploitation requires a registered user who has access to upload functionality.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2015-08-28","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2015-08-28","kind":"exploitdb","ref":"38000","stars":null,"title":"Wolf CMS - Arbitrary File Upload / Execution"},{"date":"2016-06-22","kind":"exploitdb","ref":"40004","stars":null,"title":"Wolf CMS 0.8.2 - Arbitrary File Upload (Metasploit)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"File upload in n/a","id":"CVE-2015-6568","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2015"},"n_packages":0,"n_references":7,"next":{"headline":"Race condition in n/a","id":"CVE-2015-6569"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2015-6567"},"products":["n/a"],"published":"2017-04-14","related":[{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2015-6567","kev_date_added":null,"published":"2017-04-14"},{"cvss_score":6.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2012-1897","kev_date_added":null,"published":"2012-10-01"},{"cvss_score":6.5,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-8814","kev_date_added":null,"published":"2018-04-04"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-10646","kev_date_added":null,"published":"2019-03-30"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2018-1000084","kev_date_added":null,"published":"2018-03-13"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2017-11611","kev_date_added":null,"published":"2017-09-08"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Authenticated users can upload malicious PHP files by renaming extensions, leading to remote code execution on the server.","url":"https://insights.sbomify.com/CVE-2015-6568/"}