{"answers":{"affected":"2 open source packages ship an affected version, including lavalite/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36396 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36396 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36396 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Jul 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-36396 and fix it if it is affected.\n\nWhat it is: CVE-2020-36396 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Jul 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-36396 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- lavalite/cms (Packagist): affected all versions up to 5.8.0; no fix listed\n- lavalite/cms (Packagist): affected all versions up to 5.8.0; 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-2020-36396/ (Markdown: https://insights.sbomify.com/CVE-2020-36396/index.md)","id":"CVE-2020-36396","markdown":"https://insights.sbomify.com/CVE-2020-36396/index.md","name":"CVE-2020-36396","record":{"aliases":["GHSA-gjf5-j475-p4g6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LavaLite CMS","requires_auth":"low_privilege","summary":"Authenticated attackers can execute arbitrary scripts in LavaLite via stored XSS in the role management component.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lavalite","vendor":"lavalite"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A stored cross site scripting (XSS) vulnerability in the /admin/roles/role component of LavaLite 5.8.0 allows authenticated attackers to execute arbitrary web scripts or HTML via a crafted payload entered into the \"New\" 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":false,"headline":"Stored XSS in LavaLite 5.8.0","id":"CVE-2020-36396","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"LavaLite Stored Cross-site Scripting vulnerability","id":"CVE-2020-36397"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["5.8.0"],"package":"lavalite/cms","purl":null,"source":"GHSA-gjf5-j475-p4g6"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["5.8.0"],"package":"lavalite/cms","purl":"pkg:composer/lavalite/cms","source":"GHSA-gjf5-j475-p4g6"}],"prev":{"headline":"Stored XSS in LavaLite 5.8.0","id":"CVE-2020-36395"},"products":["n/a"],"published":"2021-07-02","related":[{"cvss_score":9.8,"headline":"LavaLite vulnerable to web cache poisoning","id":"CVE-2023-27238","kev_date_added":null,"published":"2023-05-12"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2025-70866","kev_date_added":null,"published":"2026-02-13"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2023-36983","kev_date_added":null,"published":"2023-08-01"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2023-36984","kev_date_added":null,"published":"2023-08-01"},{"cvss_score":7.5,"headline":"Lavalite vulnerable to Arbitrary File Read via Directory Traversal","id":"CVE-2022-42188","kev_date_added":null,"published":"2022-10-18"},{"cvss_score":6.1,"headline":"Lavalite CMS Cross Site Scripting vulnerability","id":"CVE-2024-31828","kev_date_added":null,"published":"2024-04-26"},{"cvss_score":6.1,"headline":"LavaLite CMS vulnerable to host header injection attack","id":"CVE-2023-27237","kev_date_added":null,"published":"2023-05-12"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Authenticated attackers can execute arbitrary scripts in LavaLite via stored XSS in the role management component.","url":"https://insights.sbomify.com/CVE-2020-36396/"}