{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-15002 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15002 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15002 is a medium-severity vulnerability in Atlassian Jira Data Center, published on 11 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15002 and fix it if it is affected.\n\nWhat it is: CVE-2019-15002 is a medium-severity vulnerability in Atlassian Jira Data Center, published on 11 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-15002 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-15002/ (Markdown: https://insights.sbomify.com/CVE-2019-15002/index.md)","id":"CVE-2019-15002","markdown":"https://insights.sbomify.com/CVE-2019-15002/index.md","name":"CVE-2019-15002","record":{"aliases":["GHSA-q799-96gw-fjvp"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Atlassian Jira","requires_auth":"low_privilege","summary":"Attackers can force users to log in under an unexpected account via CSRF in the login form, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_data_center","vendor":"atlassian"},{"product":"jira_server","vendor":"atlassian"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"An exploitable CSRF vulnerability exists in Atlassian Jira, from versions 7.6.4 to 8.1.0. The login form doesn’t require a CSRF token. As a result, an attacker can log a user into the system under an unexpected account.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site request forgery in Jira Data Center","id":"CVE-2019-15002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira_data_center","products":["atlassian:jira_data_center","atlassian:jira_server"],"type":"csrf","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Jira Service Desk Data Center","id":"CVE-2019-15003"},"packages":[],"prev":{"headline":"Code injection in Jira Data Center","id":"CVE-2019-15001"},"products":["Jira Data Center","Jira Server"],"published":"2025-02-11","related":[{"cvss_score":5.3,"headline":"Atlassian Jira Server and Data Center Path Traversal","id":"CVE-2021-26086","kev_date_added":"2024-11-12","published":"2021-08-16"},{"cvss_score":9.8,"headline":"Auth bypass in Jira Core Server","id":"CVE-2022-0540","kev_date_added":null,"published":"2022-04-20"},{"cvss_score":9.8,"headline":"Deserialization in Jira Core Data Center","id":"CVE-2020-36239","kev_date_added":null,"published":"2021-07-29"},{"cvss_score":8.7,"headline":"Path traversal in Jira Software Data Center","id":"CVE-2025-22167","kev_date_added":null,"published":"2025-10-22"},{"cvss_score":7.8,"headline":"Other in Jira Server","id":"CVE-2019-20419","kev_date_added":null,"published":"2020-07-03"},{"cvss_score":7.4,"headline":"Information disclosure in Jira Core Data Center","id":"CVE-2024-21685","kev_date_added":null,"published":"2024-06-18"},{"cvss_score":7.2,"headline":"This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions: 9.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Core","id":"CVE-2025-22157","kev_date_added":null,"published":"2025-05-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-13","vendors":["Atlassian"]},"summary":"Attackers can force users to log in under an unexpected account via CSRF in the login form, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2019-15002/"}