{"answers":{"affected":"2 open source packages ship an affected version, including bolt/bolt. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4041 in the wild and no public exploit code.","fix":"Upgrade bolt/bolt to 3.7.1 or later.","what":"CVE-2020-4041 is a high-severity cross-site scripting vulnerability in bolt, published on 8 Jun 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-4041 and fix it if it is affected.\n\nWhat it is: CVE-2020-4041 is a high-severity cross-site scripting vulnerability in bolt, published on 8 Jun 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-4041 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bolt/bolt (Packagist): affected all versions; fixed in 3.7.1\n- bolt/bolt (Packagist): affected all versions; fixed in 3.7.1\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-4041/ (Markdown: https://insights.sbomify.com/CVE-2020-4041/index.md)","id":"CVE-2020-4041","markdown":"https://insights.sbomify.com/CVE-2020-4041/index.md","name":"CVE-2020-4041","record":{"aliases":["AZL-110321","GHSA-68q3-7wjp-7q3j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Bolt CMS","requires_auth":"none","summary":"Stored XSS in Bolt CMS allows attackers to inject JavaScript via renamed uploaded files, potentially leading to code execution or account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bolt","vendor":"boltcms"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"In Bolt CMS before version 3.7.1, the filename of uploaded files was vulnerable to stored XSS. It is not possible to inject javascript code in the file name when creating/uploading the file. But, once created/uploaded, it can be renamed to inject the payload in it. Additionally, the measures to prevent renaming the file to disallowed filename extensions could be circumvented. This is fixed in Bolt 3.7.1.","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":"The filename of uploaded files vulnerable to stored XSS in Bolt CMS","id":"CVE-2020-4041","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2020"},"n_packages":2,"n_references":5,"next":{"headline":"Authentication bypass in Bareos","id":"CVE-2020-4042"},"packages":[{"ecosystem":"Packagist","fixed":["3.7.1"],"introduced":["0"],"last_affected":[],"package":"bolt/bolt","purl":null,"source":"GHSA-68q3-7wjp-7q3j"},{"ecosystem":"Packagist","fixed":["3.7.1"],"introduced":["0"],"last_affected":[],"package":"bolt/bolt","purl":"pkg:composer/bolt/bolt","source":"GHSA-68q3-7wjp-7q3j"}],"prev":{"headline":"CSRF issue on preview pages in Bolt CMS","id":"CVE-2020-4040"},"products":["bolt"],"published":"2020-06-08","related":[{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2022-31321","kev_date_added":null,"published":"2022-08-01"},{"cvss_score":8.8,"headline":"Bolt Cross Site Request Forgery (CSRF)","id":"CVE-2019-10874","kev_date_added":null,"published":"2019-04-05"},{"cvss_score":8.8,"headline":"Bolt Unrestricted Upload of File with Dangerous Type","id":"CVE-2019-9185","kev_date_added":null,"published":"2019-03-07"},{"cvss_score":8.6,"headline":"CSRF issue on preview pages in Bolt CMS","id":"CVE-2020-4040","kev_date_added":null,"published":"2020-06-08"},{"cvss_score":7.5,"headline":"Bolt CMS Authenticated Remote Code Execution via Profile Injection and File Rename","id":"CVE-2025-34086","kev_date_added":null,"published":"2025-07-03"},{"cvss_score":7.5,"headline":"Path traversal in bolt/core","id":"CVE-2021-27367","kev_date_added":null,"published":"2021-02-17"}],"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":["bolt"]},"summary":"Stored XSS in Bolt CMS allows attackers to inject JavaScript via renamed uploaded files, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/CVE-2020-4041/"}