{"answers":{"affected":"2 open source packages ship an affected version, including bagisto/bagisto. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-36238 in the wild and no public exploit code.","fix":"Upgrade bagisto/bagisto to 1.3.2 or later.","what":"CVE-2023-36238 is a medium-severity vulnerability in n/a, published on 13 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-36238 and fix it if it is affected.\n\nWhat it is: CVE-2023-36238 is a medium-severity vulnerability in n/a, published on 13 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-36238 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bagisto/bagisto (Packagist): affected all versions; fixed in 1.3.2\n- bagisto/bagisto (Packagist): affected all versions; fixed in 1.3.2\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-36238/ (Markdown: https://insights.sbomify.com/CVE-2023-36238/index.md)","id":"CVE-2023-36238","markdown":"https://insights.sbomify.com/CVE-2023-36238/index.md","name":"CVE-2023-36238","record":{"aliases":["GHSA-pmc7-hmmw-g96q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Bagisto e-commerce platform","requires_auth":"low_privilege","summary":"An attacker can access sensitive invoice information by manipulating the invoice ID parameter in Bagisto.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bagisto","vendor":"webkul"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Insecure Direct Object Reference (IDOR) in Bagisto v.1.5.1 allows an attacker to obtain sensitive information via the invoice ID parameter.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Bagisto vulnerable to Insecure Direct Object Reference (IDOR)","id":"CVE-2023-36238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-36239"},"packages":[{"ecosystem":"Packagist","fixed":["1.3.2"],"introduced":["0"],"last_affected":[],"package":"bagisto/bagisto","purl":null,"source":"GHSA-pmc7-hmmw-g96q"},{"ecosystem":"Packagist","fixed":["1.3.2"],"introduced":["0"],"last_affected":[],"package":"bagisto/bagisto","purl":"pkg:composer/bagisto/bagisto","source":"GHSA-pmc7-hmmw-g96q"}],"prev":{"headline":"Bagisto Cross-Site Request Forgery vulnerability","id":"CVE-2023-36237"},"products":["n/a"],"published":"2024-03-13","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-04","vendors":["n/a"]},"summary":"An attacker can access sensitive invoice information by manipulating the invoice ID parameter in Bagisto.","url":"https://insights.sbomify.com/CVE-2023-36238/"}