{"answers":{"affected":"3 open source packages ship an affected version, including django-crm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11457 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11457 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11457 is a high-severity vulnerability in n/a, published on 27 Aug 2019. 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-2019-11457 and fix it if it is affected.\n\nWhat it is: CVE-2019-11457 is a high-severity vulnerability in n/a, published on 27 Aug 2019. 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-2019-11457 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-crm (PyPI): affected all versions up to 0.2.1; no fix listed\n- django-crm (PyPI): affected all versions up to 0.2.1; no fix listed\n- django-crm (PyPI): affected from 0.2.1; 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-2019-11457/ (Markdown: https://insights.sbomify.com/CVE-2019-11457/index.md)","id":"CVE-2019-11457","markdown":"https://insights.sbomify.com/CVE-2019-11457/index.md","name":"CVE-2019-11457","record":{"aliases":["GHSA-pg2f-r7pc-6fxx","PYSEC-2019-174"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Django CRM","requires_auth":"none","summary":"Attackers can perform unauthorized actions like password changes or data creation in MicroPyramid Django CRM via CSRF attacks.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django_crm","vendor":"micropyramid"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:R","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Multiple CSRF issues exist in MicroPyramid Django CRM 0.2.1 via /change-password-by-admin/, /api/settings/add/, /cases/create/, /change-password-by-admin/, /comment/add/, /documents/1/view/, /documents/create/, /opportunities/create/, and /login/.","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":"Cross-Site Request Forgery in MicroPyramid Django CRM","id":"CVE-2019-11457","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":3,"n_references":3,"next":{"headline":"Unsafe deserialization in SmtpTransport in CakePHP","id":"CVE-2019-11458"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.2.1"],"package":"django-crm","purl":null,"source":"GHSA-pg2f-r7pc-6fxx"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.2.1"],"package":"django-crm","purl":"pkg:pypi/django-crm","source":"GHSA-pg2f-r7pc-6fxx"},{"ecosystem":"PyPI","fixed":[],"introduced":["0.2.1"],"last_affected":[],"package":"django-crm","purl":"pkg:pypi/django-crm","source":"PYSEC-2019-174"}],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-11456"},"products":["n/a"],"published":"2019-08-27","related":[{"cvss_score":8.8,"headline":"MicroPyramid Django-CRM CSRF","id":"CVE-2018-16552","kev_date_added":null,"published":"2018-09-05"}],"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":"Attackers can perform unauthorized actions like password changes or data creation in MicroPyramid Django CRM via CSRF attacks.","url":"https://insights.sbomify.com/CVE-2019-11457/"}