{"answers":{"affected":"2 open source packages ship an affected version, including processwire/processwire. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24676 exists.","fix":"No fix has been published for CVE-2023-24676 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-24676 is a high-severity code injection vulnerability in n/a, published on 24 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-24676 and fix it if it is affected.\n\nWhat it is: CVE-2023-24676 is a high-severity code injection vulnerability in n/a, published on 24 Jan 2024. 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-2023-24676 exists.\n\nAffected packages and fixed versions:\n- processwire/processwire (Packagist): affected all versions up to 3.0.210; no fix listed\n- processwire/processwire (Packagist): affected all versions up to 3.0.210; no fix listed\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-2023-24676/ (Markdown: https://insights.sbomify.com/CVE-2023-24676/index.md)","id":"CVE-2023-24676","markdown":"https://insights.sbomify.com/CVE-2023-24676/index.md","name":"CVE-2023-24676","record":{"aliases":["GHSA-2cvg-w29m-j8xc"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ProcessWire CMS","requires_auth":"high_privilege","summary":"Administrators can execute arbitrary code via the module installation feature, though this is disputed as it aligns with intended admin privileges.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"processwire","vendor":"processwire"}],"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 found in ProcessWire 3.0.210 allows attackers to execute arbitrary code and install a reverse shell via the download_zip_url parameter when installing a new module. NOTE: this is disputed because exploitation requires that the attacker is able to enter requests as an admin; however, a ProcessWire admin is intentionally allowed to install any module that contains any arbitrary code.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Arbitrary Code Execution in Processwire","id":"CVE-2023-24676","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2023"},"n_packages":2,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2023-24678"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["3.0.210"],"package":"processwire/processwire","purl":null,"source":"GHSA-2cvg-w29m-j8xc"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["3.0.210"],"package":"processwire/processwire","purl":"pkg:composer/processwire/processwire","source":"GHSA-2cvg-w29m-j8xc"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-24675"},"products":["n/a"],"published":"2024-01-24","related":[{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2020-27467","kev_date_added":null,"published":"2022-02-22"},{"cvss_score":6.5,"headline":"ProcessWire CMS vulnerable to resource-exhaustion Denial of Service","id":"CVE-2025-60790","kev_date_added":null,"published":"2025-10-21"},{"cvss_score":6.5,"headline":"ProcessWire vulnerable to Cross-Site Request Forgery","id":"CVE-2022-40488","kev_date_added":null,"published":"2022-10-31"},{"cvss_score":6.1,"headline":"ProcessWire vulnerable to Cross-site Scripting","id":"CVE-2022-40487","kev_date_added":null,"published":"2022-10-31"},{"cvss_score":4.2,"headline":"ProcessWire Cross Site Request Forgery vulnerability","id":"CVE-2024-41597","kev_date_added":null,"published":"2024-07-19"}],"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":"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":"2025-10-17","vendors":["n/a"]},"summary":"Administrators can execute arbitrary code via the module installation feature, though this is disputed as it aligns with intended admin privileges.","url":"https://insights.sbomify.com/CVE-2023-24676/"}