{"answers":{"affected":"3 open source packages ship an affected version, including mezzanine and Mezzanine. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-19002 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-19002 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-19002 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Aug 2021. 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-19002 and fix it if it is affected.\n\nWhat it is: CVE-2020-19002 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Aug 2021. 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-19002 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mezzanine (PyPI): affected all versions; no fix listed\n- mezzanine (PyPI): affected all versions up to 6.0.0; no fix listed\n- Mezzanine (PyPI): affected all versions up to 6.0.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-19002/ (Markdown: https://insights.sbomify.com/CVE-2020-19002/index.md)","id":"CVE-2020-19002","markdown":"https://insights.sbomify.com/CVE-2020-19002/index.md","name":"CVE-2020-19002","record":{"aliases":["GHSA-fpv7-hx6r-9vcx","PYSEC-2021-343"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Mezzanine CMS","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via XSS in the Mezzanine CMS admin blog post description field.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mezzanine","vendor":"jupo"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"Cross Site Scripting (XSS) in Mezzanine v4.3.1 allows remote attackers to execute arbitrary code via the 'Description' field of the component 'admin/blog/blogpost/add/'. This issue is different than CVE-2018-16632.","ecosystems":["PyPI"],"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":"Mezzanine Cross Site Scripting (XSS) vulnerability","id":"CVE-2020-19002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xss","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"Verification check bypass in Gate One","id":"CVE-2020-19003"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["6.0.0"],"package":"Mezzanine","purl":null,"source":"GHSA-fpv7-hx6r-9vcx"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":[],"package":"mezzanine","purl":"pkg:pypi/mezzanine","source":"PYSEC-2021-343"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["6.0.0"],"package":"mezzanine","purl":"pkg:pypi/mezzanine","source":"GHSA-fpv7-hx6r-9vcx"}],"prev":{"headline":"Command Injection in Simiki","id":"CVE-2020-19001"},"products":["n/a"],"published":"2021-08-27","related":[{"cvss_score":9.8,"headline":"Mezzanine allows attackers to bypass access control mechanisms","id":"CVE-2024-25169","kev_date_added":null,"published":"2024-02-28"},{"cvss_score":9.1,"headline":"Mezzanine allows attackers to bypass access controls via manipulating the Host header","id":"CVE-2024-25170","kev_date_added":null,"published":"2024-02-28"},{"cvss_score":6.1,"headline":"Mezzanine CMS Cross-Site Scripting (XSS) vulnerability","id":"CVE-2025-29573","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":4.8,"headline":"Mezzanine CMS vulnerable to Cross-site Scripting","id":"CVE-2025-50481","kev_date_added":null,"published":"2025-07-23"},{"cvss_score":4.8,"headline":"Stored Cross-Site Scripting (XSS) in Mezzanine CMS Admin Interface","id":"CVE-2025-6050","kev_date_added":null,"published":"2025-06-17"},{"cvss_score":4.8,"headline":"Cross-site scripting in n/a","id":"CVE-2018-16632","kev_date_added":null,"published":"2018-12-28"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"Remote attackers can execute arbitrary code via XSS in the Mezzanine CMS admin blog post description field.","url":"https://insights.sbomify.com/CVE-2020-19002/"}