{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-15001 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15001 is a high-severity code injection vulnerability in Atlassian Jira Data Center, published on 19 Sep 2019. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15001 and fix it if it is affected.\n\nWhat it is: CVE-2019-15001 is a high-severity code injection vulnerability in Atlassian Jira Data Center, published on 19 Sep 2019. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-15001 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-15001/ (Markdown: https://insights.sbomify.com/CVE-2019-15001/index.md)","id":"CVE-2019-15001","markdown":"https://insights.sbomify.com/CVE-2019-15001/index.md","name":"CVE-2019-15001","record":{"aliases":["GHSA-v4p4-65gh-94f7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira Server","requires_auth":"high_privilege","summary":"Administrators can achieve remote code execution via template injection in the Jira Importers Plugin, requiring immediate upgrades.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"jira_data_center","vendor":"atlassian"},{"product":"jira_server","vendor":"atlassian"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The Jira Importers Plugin in Atlassian Jira Server and Data Cente from version with 7.0.10 before 7.6.16, from 7.7.0 before 7.13.8, from 8.0.0 before 8.1.3, from 8.2.0 before 8.2.5, from 8.3.0 before 8.3.4 and from 8.4.0 before 8.4.1 allows remote attackers with Administrator permissions to gain remote code execution via a template injection vulnerability through the use of a crafted PUT request.","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":"Code injection in Jira Data Center","id":"CVE-2019-15001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira_data_center","products":["atlassian:jira_data_center","atlassian:jira_server"],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site request forgery in Jira Data Center","id":"CVE-2019-15002"},"packages":[],"prev":{"headline":"Command injection in Bitbucket Data Center","id":"CVE-2019-15000"},"products":["Jira Data Center","Jira Server"],"published":"2019-09-19","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Atlassian"]},"summary":"Administrators can achieve remote code execution via template injection in the Jira Importers Plugin, requiring immediate upgrades.","url":"https://insights.sbomify.com/CVE-2019-15001/"}