{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-3926 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-3926 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-3926 is a high-severity vulnerability in n/a, published on 1 Jul 2013. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-3926 and fix it if it is affected.\n\nWhat it is: CVE-2013-3926 is a high-severity vulnerability in n/a, published on 1 Jul 2013. It can be exploited over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-3926 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2013-3926/ (Markdown: https://insights.sbomify.com/CVE-2013-3926/index.md)","id":"CVE-2013-3926","markdown":"https://insights.sbomify.com/CVE-2013-3926/index.md","name":"CVE-2013-3926","record":{"aliases":["GHSA-9fh4-qmm7-wrrj"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Atlassian Crowd","requires_auth":"unknown","summary":"Unverified claim of remote command execution in Atlassian Crowd via a symmetric backdoor, with vendor unable to reproduce the issue.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"crowd","vendor":"atlassian"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Atlassian Crowd 2.6.3 allows remote attackers to execute arbitrary commands via unspecified vectors related to a \"symmetric backdoor.\"  NOTE: as of 20130704, the vendor could not reproduce the issue, stating \"We've been unable to substantiate the existence of [CVE-2013-3926]. The author of the article has not contacted Atlassian and has provided no detail, making it difficult to validate the claim... If we can confirm that there is a vulnerability, a patch will be issued.","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":"Other in n/a","id":"CVE-2013-3926","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2013"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2013-3927"},"packages":[],"prev":{"headline":"Atlassian Crowd 2.5.x before 2.5.4, 2.6.x before 2.6.3, 2.3.8, and 2.4.9 allows remote attackers to read arbitrary files and send HTTP reque","id":"CVE-2013-3925"},"products":["n/a"],"published":"2013-07-01","related":[{"cvss_score":9.8,"headline":"Atlassian Crowd and Crowd Data Center Remote Code Execution","id":"CVE-2019-11580","kev_date_added":"2021-11-03","published":"2019-06-03"},{"cvss_score":9.8,"headline":"Auth bypass in Crowd Data Center","id":"CVE-2022-43782","kev_date_added":null,"published":"2022-11-17"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2016-6496","kev_date_added":null,"published":"2016-12-09"},{"cvss_score":8.1,"headline":"Auth bypass in Crowd","id":"CVE-2017-18105","kev_date_added":null,"published":"2019-03-29"},{"cvss_score":8.1,"headline":"Auth bypass in Crowd","id":"CVE-2018-20238","kev_date_added":null,"published":"2019-02-13"},{"cvss_score":8,"headline":"Code injection in Crowd Data Center","id":"CVE-2023-22521","kev_date_added":null,"published":"2023-11-21"},{"cvss_score":7.9,"headline":"XML external entity in Crowd Data Center","id":"CVE-2026-21569","kev_date_added":null,"published":"2026-01-28"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Unverified claim of remote command execution in Atlassian Crowd via a symmetric backdoor, with vendor unable to reproduce the issue.","url":"https://insights.sbomify.com/CVE-2013-3926/"}