{"answers":{"affected":"3 open source packages ship an affected version, including django-widgy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-18704 in the wild and no public exploit code.","fix":"Upgrade django-widgy to 0.9.0 or later.","what":"CVE-2020-18704 is a critical vulnerability in n/a, published on 16 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-18704 and fix it if it is affected.\n\nWhat it is: CVE-2020-18704 is a critical vulnerability in n/a, published on 16 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-18704 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-widgy (PyPI): affected all versions; fixed in 0.9.0\n- django-widgy (PyPI): affected all versions; fixed in 0.9.0\n- django-widgy (PyPI): affected all versions; fixed in 0.9.0\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-2020-18704/ (Markdown: https://insights.sbomify.com/CVE-2020-18704/index.md)","id":"CVE-2020-18704","markdown":"https://insights.sbomify.com/CVE-2020-18704/index.md","name":"CVE-2020-18704","record":{"aliases":["GHSA-98hv-qff3-8793","PYSEC-2021-336"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Django Widgy plugin","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by uploading malicious files via the image widget in the Django-Widgy plugin.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"widgy","vendor":"fusionbox"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Unrestricted Upload of File with Dangerous Type in Django-Widgy v0.8.4 allows remote attackers to execute arbitrary code via the 'image' widget in the component 'Change Widgy Page'.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Unrestricted Upload of File with Dangerous Type in django-widgy","id":"CVE-2020-18704","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"file_upload","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"Improper Restriction of XML External Entity Reference in Quokka","id":"CVE-2020-18705"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.0"],"introduced":["0"],"last_affected":[],"package":"django-widgy","purl":null,"source":"GHSA-98hv-qff3-8793"},{"ecosystem":"PyPI","fixed":["0.9.0"],"introduced":["0"],"last_affected":[],"package":"django-widgy","purl":"pkg:pypi/django-widgy","source":"GHSA-98hv-qff3-8793"},{"ecosystem":"PyPI","fixed":["0.9.0"],"introduced":["0"],"last_affected":[],"package":"django-widgy","purl":"pkg:pypi/django-widgy","source":"PYSEC-2021-336"}],"prev":{"headline":"Improper Restriction of XML External Entity Reference in Quokka","id":"CVE-2020-18703"},"products":["n/a"],"published":"2021-08-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-08-04","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by uploading malicious files via the image widget in the Django-Widgy plugin.","url":"https://insights.sbomify.com/CVE-2020-18704/"}