{"answers":{"affected":"2 open source packages ship an affected version, including pyrocms/pyrocms. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29689 exists.","fix":"No fix has been published for CVE-2023-29689 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-29689 is a critical code injection vulnerability in n/a, published on 4 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-29689 and fix it if it is affected.\n\nWhat it is: CVE-2023-29689 is a critical code injection vulnerability in n/a, published on 4 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29689 exists.\n\nAffected packages and fixed versions:\n- pyrocms/pyrocms (Packagist): affected all versions up to 3.9; no fix listed\n- pyrocms/pyrocms (Packagist): affected all versions up to 3.9; 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-29689/ (Markdown: https://insights.sbomify.com/CVE-2023-29689/index.md)","id":"CVE-2023-29689","markdown":"https://insights.sbomify.com/CVE-2023-29689/index.md","name":"CVE-2023-29689","record":{"aliases":["GHSA-w7vm-4v3j-vgpw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PyroCMS","requires_auth":"none","summary":"Attackers can execute arbitrary code on PyroCMS servers via server-side template injection, requiring immediate patching.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pyrocms","vendor":"pyrocms"}],"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":[],"description":"PyroCMS 3.9 contains a remote code execution (RCE) vulnerability that can be exploited through a server-side template injection (SSTI) flaw. This vulnerability allows a malicious attacker to send customized commands to the server and execute arbitrary code on the affected system.","ecosystems":["Packagist"],"exploits":{"exploitdb":1,"first_seen":"2023-08-08","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-08-08","kind":"exploitdb","ref":"51669","stars":null,"title":"Pyro CMS 3.9 - Server-Side Template Injection (SSTI) (Authenticated)"},{"date":"2026-01-09T18:32:49Z","kind":"github_poc","ref":"https://github.com/YSaxon/pyrocms-ssti-fix","stars":0,"title":"A drop-in fix for CVE-2023-29689 - SSTI in PyroCMS, via a custom Twig Sandbox implementation"}],"tier":"weaponised"},"has_fix":false,"headline":"PyroCMS remote code execution vulnerability","id":"CVE-2023-29689","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-29693"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["3.9"],"package":"pyrocms/pyrocms","purl":null,"source":"GHSA-w7vm-4v3j-vgpw"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["3.9"],"package":"pyrocms/pyrocms","purl":"pkg:composer/pyrocms/pyrocms","source":"GHSA-w7vm-4v3j-vgpw"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2023-29681"},"products":["n/a"],"published":"2023-08-04","related":[{"cvss_score":9,"headline":"PyroCMS vulnerable to stored Cross Site Scripting","id":"CVE-2022-37721","kev_date_added":null,"published":"2022-11-25"},{"cvss_score":7.1,"headline":"PyroCMS Vulnerable to CSRF","id":"CVE-2020-25263","kev_date_added":null,"published":"2020-10-08"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2022-35118","kev_date_added":null,"published":"2022-08-01"},{"cvss_score":5.3,"headline":"PyroCMS v3.0.1 Stored Cross-Site Scripting via Admin Redirects","id":"CVE-2024-58297","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":4.3,"headline":"PyroCMS Vulnerable to CSRF","id":"CVE-2020-25262","kev_date_added":null,"published":"2020-10-08"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-17","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code on PyroCMS servers via server-side template injection, requiring immediate patching.","url":"https://insights.sbomify.com/CVE-2023-29689/"}