{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-31739 exists.","fix":"No fix has been published for CVE-2021-31739 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-31739 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-31739 and fix it if it is affected.\n\nWhat it is: CVE-2021-31739 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-31739 exists.\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-2021-31739/ (Markdown: https://insights.sbomify.com/CVE-2021-31739/index.md)","id":"CVE-2021-31739","markdown":"https://insights.sbomify.com/CVE-2021-31739/index.md","name":"CVE-2021-31739","record":{"aliases":["GHSA-5q2f-65mc-6jvf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SEPPmail email security","requires_auth":"none","summary":"An attacker can inject malicious scripts via recipient addresses in SEPPmail, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"seppmail","vendor":"seppmail"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"The SEPPmail solution is vulnerable to a Cross-Site Scripting vulnerability (XSS), because user input is not correctly encoded in HTML attributes when returned by the server.SEPPmail 11.1.10 allows XSS via a recipient address.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2021-31739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-31740"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-31738"},"products":["n/a"],"published":"2022-11-18","related":[{"cvss_score":10,"headline":"SEPPmail User Web Interface Arbitrary File Write to RCE","id":"CVE-2026-2743","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":9.5,"headline":"PDF Password CMDi","id":"CVE-2026-27441","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":9.3,"headline":"zip_attachments Path Traversal","id":"CVE-2026-27442","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":8.2,"headline":"S/MIME Decryption Tag Sanitization Bypass","id":"CVE-2026-27443","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":7.8,"headline":"Header Email Address Parsing","id":"CVE-2026-27444","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":7.8,"headline":"S/MIME Certificate Subject Whitespace","id":"CVE-2026-2748","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":6.9,"headline":"PGP Signature Reflection","id":"CVE-2026-27445","kev_date_added":null,"published":"2026-03-04"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-29","vendors":["n/a"]},"summary":"An attacker can inject malicious scripts via recipient addresses in SEPPmail, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2021-31739/"}