{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-68643 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-68643 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68643 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Feb 2026. 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-2025-68643 and fix it if it is affected.\n\nWhat it is: CVE-2025-68643 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Feb 2026. 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-2025-68643 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-2025-68643/ (Markdown: https://insights.sbomify.com/CVE-2025-68643/index.md)","id":"CVE-2025-68643","markdown":"https://insights.sbomify.com/CVE-2025-68643/index.md","name":"CVE-2025-68643","record":{"aliases":["GHSA-2vf2-fx97-xpqj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Mail Server","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary scripts in victims' browsers via stored XSS in the timeFormat preference, potentially leading to account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"axigen_mail_server","vendor":"axigen"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","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":"Axigen Mail Server before 10.5.57 allows stored Cross-Site Scripting (XSS) in the handling of the timeFormat account preference parameter. Attackers can exploit this by deploying a multi-stage attack. In the first stage, a malicious JavaScript payload is injected into the timeFormat preference by exploiting a separate vulnerability or using compromised credentials. In the second stage, when the victim logs into the WebMail interface, the unsanitized timeFormat value is loaded from storage and inserted into the DOM, causing the injected script to execute.","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-2025-68643","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in RPS","id":"CVE-2025-68644"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-68640"},"products":["n/a"],"published":"2026-02-05","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2023-23566","kev_date_added":null,"published":"2023-01-13"},{"cvss_score":9.6,"headline":"Cross-site scripting in n/a","id":"CVE-2023-48974","kev_date_added":null,"published":"2024-02-08"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2020-26942","kev_date_added":null,"published":"2024-03-06"},{"cvss_score":9,"headline":"Cross-site scripting in n/a","id":"CVE-2025-68723","kev_date_added":null,"published":"2026-02-05"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-68722","kev_date_added":null,"published":"2026-02-05"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2025-68721","kev_date_added":null,"published":"2026-02-05"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-11","vendors":["n/a"]},"summary":"Attackers can execute arbitrary scripts in victims' browsers via stored XSS in the timeFormat preference, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2025-68643/"}