{"answers":{"affected":"2 open source packages ship an affected version, including bagisto/bagisto. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21449 exists.","fix":"Upgrade bagisto/bagisto to 2.3.10 or later.","what":"CVE-2026-21449 is a high-severity code injection vulnerability in bagisto, published on 2 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-21449 and fix it if it is affected.\n\nWhat it is: CVE-2026-21449 is a high-severity code injection vulnerability in bagisto, published on 2 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21449 exists.\n\nAffected packages and fixed versions:\n- bagisto/bagisto (Packagist): affected all versions; fixed in 2.3.10\n- bagisto/bagisto (Packagist): affected all versions; fixed in 2.3.10\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-2026-21449/ (Markdown: https://insights.sbomify.com/CVE-2026-21449/index.md)","id":"CVE-2026-21449","markdown":"https://insights.sbomify.com/CVE-2026-21449/index.md","name":"CVE-2026-21449","record":{"aliases":["GHSA-mqhg-v22x-pqj8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Bagisto eCommerce platform","requires_auth":"low_privilege","summary":"Low-privilege users can execute arbitrary code via server-side template injection in Bagisto by manipulating name fields.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bagisto","vendor":"webkul"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-1336","name":"Improper Neutralization of Special Elements Used in a Template Engine"}],"description":"Bagisto is an open source laravel eCommerce platform. Versions prior to 2.3.10 are vulnerable to server-side template injection via first name and last name from a low-privilege user. Version 2.3.10 fixes the issue.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Bagisto has SSTI via first and last name from low-privilege user (not admin)","id":"CVE-2026-21449","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Bagisto has SSTI in parameter that can lead to RCE","id":"CVE-2026-21450"},"packages":[{"ecosystem":"Packagist","fixed":["2.3.10"],"introduced":["0"],"last_affected":[],"package":"bagisto/bagisto","purl":null,"source":"GHSA-mqhg-v22x-pqj8"},{"ecosystem":"Packagist","fixed":["2.3.10"],"introduced":["0"],"last_affected":[],"package":"bagisto/bagisto","purl":"pkg:composer/bagisto/bagisto","source":"GHSA-mqhg-v22x-pqj8"}],"prev":{"headline":"Bagisto has Normal \u0026 Blind SSTI from low-privilege user when ordering product","id":"CVE-2026-21448"},"products":["bagisto"],"published":"2026-01-02","related":[{"cvss_score":8.9,"headline":"Bagisto has Normal \u0026 Blind SSTI from low-privilege user when ordering product","id":"CVE-2026-21448","kev_date_added":null,"published":"2026-01-02"},{"cvss_score":8.8,"headline":"Bagisto Missing Authentication on Installer API Endpoints","id":"CVE-2026-21446","kev_date_added":null,"published":"2026-01-02"},{"cvss_score":8.8,"headline":"Bagisto Cross-Site Request Forgery vulnerability","id":"CVE-2023-36237","kev_date_added":null,"published":"2024-02-26"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2023-33570","kev_date_added":null,"published":"2023-06-28"},{"cvss_score":8.8,"headline":"Authorization Bypass Through User-Controlled Key in Bagisto","id":"CVE-2019-16403","kev_date_added":null,"published":"2019-09-18"},{"cvss_score":8.8,"headline":"Bagisto CSRF Vulnerability","id":"CVE-2019-14933","kev_date_added":null,"published":"2019-08-11"},{"cvss_score":8.3,"headline":"Bagisto is vulnerable to XSS through Admin Panel's product creation path","id":"CVE-2025-60880","kev_date_added":null,"published":"2025-10-10"}],"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":"2026-01-02","vendors":["bagisto"]},"summary":"Low-privilege users can execute arbitrary code via server-side template injection in Bagisto by manipulating name fields.","url":"https://insights.sbomify.com/CVE-2026-21449/"}