{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-20918 exists.","fix":"No fix has been published for CVE-2020-20918 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-20918 is a high-severity code injection vulnerability in n/a, published on 20 Jun 2023. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-20918 and fix it if it is affected.\n\nWhat it is: CVE-2020-20918 is a high-severity code injection vulnerability in n/a, published on 20 Jun 2023. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-20918 exists.\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-20918/ (Markdown: https://insights.sbomify.com/CVE-2020-20918/index.md)","id":"CVE-2020-20918","markdown":"https://insights.sbomify.com/CVE-2020-20918/index.md","name":"CVE-2020-20918","record":{"aliases":["GHSA-5jr5-6wr3-298c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Pluck CMS","requires_auth":"high_privilege","summary":"Remote attackers can execute arbitrary PHP code in Pluck CMS by manipulating the hidden parameter during page editing.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pluck","vendor":"pluck-cms"}],"cvss":{"score":7.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"An issue discovered in Pluck CMS v.4.7.10-dev2 allows a remote attacker to execute arbitrary php code via the hidden parameter to admin.php when editing a page.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Code injection in n/a","id":"CVE-2020-20918","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2020-20919"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2020-20915"},"products":["n/a"],"published":"2023-06-20","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2024-43042","kev_date_added":null,"published":"2024-08-16"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2021-31746","kev_date_added":null,"published":"2021-12-10"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-20951","kev_date_added":null,"published":"2021-05-18"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2019-11344","kev_date_added":null,"published":"2019-04-19"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2018-11736","kev_date_added":null,"published":"2018-06-05"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2018-11331","kev_date_added":null,"published":"2018-05-21"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2014-8708","kev_date_added":null,"published":"2017-03-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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-12-10","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary PHP code in Pluck CMS by manipulating the hidden parameter during page editing.","url":"https://insights.sbomify.com/CVE-2020-20918/"}