{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-27509 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-27509 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-27509 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jun 2022. 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-2020-27509 and fix it if it is affected.\n\nWhat it is: CVE-2020-27509 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Jun 2022. 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-2020-27509 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-2020-27509/ (Markdown: https://insights.sbomify.com/CVE-2020-27509/index.md)","id":"CVE-2020-27509","markdown":"https://insights.sbomify.com/CVE-2020-27509/index.md","name":"CVE-2020-27509","record":{"aliases":["GHSA-7g3q-7795-xgcj"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Secure Mail Client","requires_auth":"low_privilege","summary":"Attackers can hijack user accounts by injecting persistent XSS payloads into email subject fields, which execute upon recipient login.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"galaxkey","vendor":"galaxkey"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Persistent XSS in Galaxkey Secure Mail Client in Galaxkey up to 5.6.11.5 allows an attacker to perform an account takeover by intercepting the HTTP Post request when sending an email and injecting a specially crafted XSS payload in the 'subject' field. The payload executes when the recipient logs into their mailbox.","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 scripting in n/a","id":"CVE-2020-27509","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2020-27511"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-27508"},"products":["n/a"],"published":"2022-06-26","related":[],"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":"2026-07-09","vendors":["n/a"]},"summary":"Attackers can hijack user accounts by injecting persistent XSS payloads into email subject fields, which execute upon recipient login.","url":"https://insights.sbomify.com/CVE-2020-27509/"}