{"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-21451 exists.","fix":"Upgrade bagisto/bagisto to 2.3.10 or later.","what":"CVE-2026-21451 is a medium-severity cross-site scripting vulnerability in bagisto, published on 2 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-21451 and fix it if it is affected.\n\nWhat it is: CVE-2026-21451 is a medium-severity cross-site scripting vulnerability in bagisto, published on 2 Jan 2026. 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-2026-21451 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-21451/ (Markdown: https://insights.sbomify.com/CVE-2026-21451/index.md)","id":"CVE-2026-21451","markdown":"https://insights.sbomify.com/CVE-2026-21451/index.md","name":"CVE-2026-21451","record":{"aliases":["GHSA-2mwc-h2mg-v6p8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Bagisto eCommerce platform","requires_auth":"high_privilege","summary":"Attackers can bypass HTML filters in the CMS editor to inject malicious scripts, leading to administrator account takeover and backend hijacking.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bagisto","vendor":"webkul"}],"cvss":{"score":5.2,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Bagisto is an open source laravel eCommerce platform. A stored Cross-Site Scripting (XSS) vulnerability exists in Bagisto prior to version 2.3.10 within the CMS page editor. Although the platform normally attempts to sanitize `\u003cscript\u003e` tags, the filtering can be bypassed by manipulating the raw HTTP POST request before submission. As a result, arbitrary JavaScript can be stored in the CMS content and executed whenever the page is viewed or edited. This exposes administrators to a high-severity risk, including complete account takeover, backend hijacking, and malicious script execution. 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 HTML Filter Bypass that Enables Stored XSS","id":"CVE-2026-21451","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"MessagePack for Java Vulnerable to Remote DoS via Malicious EXT Payload Allocation","id":"CVE-2026-21452"},"packages":[{"ecosystem":"Packagist","fixed":["2.3.10"],"introduced":["0"],"last_affected":[],"package":"bagisto/bagisto","purl":null,"source":"GHSA-2mwc-h2mg-v6p8"},{"ecosystem":"Packagist","fixed":["2.3.10"],"introduced":["0"],"last_affected":[],"package":"bagisto/bagisto","purl":"pkg:composer/bagisto/bagisto","source":"GHSA-2mwc-h2mg-v6p8"}],"prev":{"headline":"Bagisto has SSTI in parameter that can lead to RCE","id":"CVE-2026-21450"},"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":"partial"},"state":"PUBLISHED","updated":"2026-01-02","vendors":["bagisto"]},"summary":"Attackers can bypass HTML filters in the CMS editor to inject malicious scripts, leading to administrator account takeover and backend hijacking.","url":"https://insights.sbomify.com/CVE-2026-21451/"}