{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2021-26071 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-26071 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-26071 is a low-severity vulnerability in Atlassian Jira, published on 1 Apr 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-26071 and fix it if it is affected.\n\nWhat it is: CVE-2021-26071 is a low-severity vulnerability in Atlassian Jira, published on 1 Apr 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-26071 in the wild and no public exploit code.\n\nAffected product: Atlassian Jira. 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-2021-26071/ (Markdown: https://insights.sbomify.com/CVE-2021-26071/index.md)","id":"CVE-2021-26071","markdown":"https://insights.sbomify.com/CVE-2021-26071/index.md","name":"CVE-2021-26071","record":{"aliases":["GHSA-3v9q-ffv3-hg8c"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira Server","requires_auth":"low_privilege","summary":"Remote anonymous attackers can enable or disable Jira Software configuration features via a cross-site request forgery vulnerability.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"atlassian","cpe":[{"product":"data_center","vendor":"atlassian"},{"product":"jira","vendor":"atlassian"},{"product":"jira_data_center","vendor":"atlassian"},{"product":"jira_server","vendor":"atlassian"}],"cvss":{"score":3.5,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The SetFeatureEnabled.jspa resource in Jira Server and Data Center before version 8.5.13, from version 8.6.0 before version 8.13.5, and from version 8.14.0 before version 8.15.1 allows remote anonymous attackers to enable and disable Jira Software configuration via a cross-site request forgery (CSRF) vulnerability.","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-2021-26071","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"atlassian:jira","products":["atlassian:jira","atlassian:jira_data_center","atlassian:jira_server"],"type":"csrf","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Server-side request forgery in Confluence Data Center","id":"CVE-2021-26072"},"packages":[],"prev":{"headline":"Auth bypass in Jira Data Center","id":"CVE-2021-26070"},"products":["Jira Data Center","Jira Server"],"published":"2021-04-01","related":[{"cvss_score":8.8,"headline":"Code injection in Jira Data Center","id":"CVE-2017-18113","kev_date_added":null,"published":"2021-08-02"},{"cvss_score":7.5,"headline":"Auth bypass in Jira Data Center","id":"CVE-2021-41312","kev_date_added":null,"published":"2021-11-03"},{"cvss_score":7.5,"headline":"Denial of service in Jira Data Center","id":"CVE-2021-39123","kev_date_added":null,"published":"2021-09-14"},{"cvss_score":7.5,"headline":"Missing authorization in Jira Data Center","id":"CVE-2021-39113","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":7.2,"headline":"Code injection in Jira Data Center","id":"CVE-2021-43947","kev_date_added":null,"published":"2022-01-06"},{"cvss_score":7.2,"headline":"Auth bypass in Jira Data Center","id":"CVE-2021-26070","kev_date_added":null,"published":"2021-03-22"},{"cvss_score":6.1,"headline":"Cross-site scripting in Jira Data Center","id":"CVE-2021-41304","kev_date_added":null,"published":"2021-10-26"}],"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-17","vendors":["Atlassian"]},"summary":"Remote anonymous attackers can enable or disable Jira Software configuration features via a cross-site request forgery vulnerability.","url":"https://insights.sbomify.com/CVE-2021-26071/"}