{"answers":{"affected":"5 open source packages ship an affected version, including django-cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-5081 in the wild and no public exploit code.","fix":"Upgrade django-cms to a fixed version for your release line: 3.0.14 or 3.1.1.","what":"CVE-2015-5081 is a high-severity vulnerability in n/a, published on 18 Aug 2017. 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-2015-5081 and fix it if it is affected.\n\nWhat it is: CVE-2015-5081 is a high-severity vulnerability in n/a, published on 18 Aug 2017. 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-2015-5081 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-cms (PyPI): affected all versions; fixed in 3.0.14, 3.1.1\n- django-cms (PyPI): affected all versions; fixed in 3.0.14\n- django-cms (PyPI): affected all versions; fixed in 3.0.14\n- django-cms (PyPI): affected from 3.1.0b1; fixed in 3.1.1\n- django-cms (PyPI): affected from 3.1.0b1; fixed in 3.1.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-2015-5081/ (Markdown: https://insights.sbomify.com/CVE-2015-5081/index.md)","id":"CVE-2015-5081","markdown":"https://insights.sbomify.com/CVE-2015-5081/index.md","name":"CVE-2015-5081","record":{"aliases":["GHSA-2pqc-gv8q-pvqv","PYSEC-2017-11"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"django CMS","requires_auth":"none","summary":"Remote attackers can trick privileged users into performing unintended actions in django CMS, potentially leading to account takeover or data modification.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django_cms","vendor":"django-cms"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-site request forgery (CSRF) vulnerability in django CMS before 3.0.14, 3.1.x before 3.1.1 allows remote attackers to manipulate privileged users into performing unknown actions via unspecified vectors.","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":true,"headline":"django-cms CSRF Vulnerability","id":"CVE-2015-5081","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"csrf","year":"2015"},"n_packages":5,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2015-5082"},"packages":[{"ecosystem":"PyPI","fixed":["3.0.14","3.1.1"],"introduced":["0","3.1"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"PYSEC-2017-11"},{"ecosystem":"PyPI","fixed":["3.0.14"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":null,"source":"GHSA-2pqc-gv8q-pvqv"},{"ecosystem":"PyPI","fixed":["3.0.14"],"introduced":["0"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"GHSA-2pqc-gv8q-pvqv"},{"ecosystem":"PyPI","fixed":["3.1.1"],"introduced":["3.1.0b1"],"last_affected":[],"package":"django-cms","purl":null,"source":"GHSA-2pqc-gv8q-pvqv"},{"ecosystem":"PyPI","fixed":["3.1.1"],"introduced":["3.1.0b1"],"last_affected":[],"package":"django-cms","purl":"pkg:pypi/django-cms","source":"GHSA-2pqc-gv8q-pvqv"}],"prev":{"headline":"Command injection in n/a","id":"CVE-2015-5080"},"products":["n/a"],"published":"2017-08-18","related":[{"cvss_score":5.4,"headline":"Cross-site Scripting in django-cms","id":"CVE-2021-44649","kev_date_added":null,"published":"2022-01-12"},{"cvss_score":4.8,"headline":"Stored XSS in Open Source Project \"django-cms\"","id":"CVE-2024-11319","kev_date_added":null,"published":"2024-11-18"}],"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-06","vendors":["n/a"]},"summary":"Remote attackers can trick privileged users into performing unintended actions in django CMS, potentially leading to account takeover or data modification.","url":"https://insights.sbomify.com/CVE-2015-5081/"}