{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2020-35945 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35945 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35945 is a critical vulnerability in n/a, published on 1 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-35945 and fix it if it is affected.\n\nWhat it is: CVE-2020-35945 is a critical vulnerability in n/a, published on 1 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-35945 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-2020-35945/ (Markdown: https://insights.sbomify.com/CVE-2020-35945/index.md)","id":"CVE-2020-35945","markdown":"https://insights.sbomify.com/CVE-2020-35945/index.md","name":"CVE-2020-35945","record":{"aliases":["GHSA-v452-696f-f255"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress Divi Builder","requires_auth":"low_privilege","summary":"Authenticated contributors can upload arbitrary PHP files due to client-side validation, enabling remote code execution on WordPress sites using Divi.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"divi","vendor":"elegantthemes"},{"product":"divi_builder","vendor":"elegantthemes"},{"product":"extra","vendor":"elegantthemes"}],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:C/UI:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"An issue was discovered in the Divi Builder plugin, Divi theme, and Divi Extra theme before 4.5.3 for WordPress. Authenticated attackers, with contributor-level or above capabilities, can upload arbitrary files, including .php files. This occurs because the check for file extensions is on the client side.","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-2020-35945","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-35946"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-35944"},"products":["n/a"],"published":"2021-01-01","related":[{"cvss_score":6.5,"headline":"WordPress Divi Theme \u003c= 4.20.2 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-29099","kev_date_added":null,"published":"2023-08-08"},{"cvss_score":6.4,"headline":"Divi \u003c= 4.25.1 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-5533","kev_date_added":null,"published":"2024-06-18"},{"cvss_score":6.4,"headline":"Divi \u003c= 4.23.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2023-6744","kev_date_added":null,"published":"2023-12-23"},{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2015-1579","kev_date_added":null,"published":"2015-02-11"}],"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-08-04","vendors":["n/a"]},"summary":"Authenticated contributors can upload arbitrary PHP files due to client-side validation, enabling remote code execution on WordPress sites using Divi.","url":"https://insights.sbomify.com/CVE-2020-35945/"}