{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-41959 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-41959 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-41959 is a high-severity cross-site scripting vulnerability in mailcow-dockerized, published on 5 Aug 2024. 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-2024-41959 and fix it if it is affected.\n\nWhat it is: CVE-2024-41959 is a high-severity cross-site scripting vulnerability in mailcow-dockerized, published on 5 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-41959 in the wild and no public exploit code.\n\nAffected product: mailcow-dockerized. 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-2024-41959/ (Markdown: https://insights.sbomify.com/CVE-2024-41959/index.md)","id":"CVE-2024-41959","markdown":"https://insights.sbomify.com/CVE-2024-41959/index.md","name":"CVE-2024-41959","record":{"aliases":["GHSA-v3r3-8f69-ph29"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"mailcow email suite","requires_auth":"none","summary":"An unauthenticated attacker can inject JavaScript into API logs, leading to script execution in the victim's browser, potentially causing data theft or unauthorized actions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mailcow\\","vendor":"mailcow"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"mailcow: dockerized is an open source groupware/email suite based on docker. An unauthenticated attacker can inject a JavaScript payload into the API logs. This payload is executed whenever the API logs page is viewed, potentially allowing an attacker to run malicious scripts in the context of the user's browser. This could lead to unauthorized actions, data theft, or further exploitation of the affected system. This issue has been addressed in the `2024-07` release. All users are advised to upgrade. There are no known workarounds for this 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":false,"headline":"Cross-site Scripting (XSS) via API Logs in mailcow: dockerized","id":"CVE-2024-41959","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site Scripting (XSS) via Relay Hosts Configuration in mailcow: dockerized","id":"CVE-2024-41960"},"packages":[],"prev":{"headline":"Two-Factor Authentication (2FA) Bypass in mailcow: dockerized","id":"CVE-2024-41958"},"products":["mailcow-dockerized"],"published":"2024-08-05","related":[{"cvss_score":9.1,"headline":"mailcow: dockerized vulnerable to SSTI in Quota and Quarantine Notification Template","id":"CVE-2025-53909","kev_date_added":null,"published":"2025-07-17"},{"cvss_score":8.8,"headline":"Mailcow Docker Container Exposure to Local Network","id":"CVE-2024-24760","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":8.8,"headline":"Manipulation of Internal Dovecot Variables in mailcow via crafted Passwords","id":"CVE-2023-34108","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":8.8,"headline":"OS Command Injection in mailcow","id":"CVE-2022-31138","kev_date_added":null,"published":"2022-07-11"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2022-31245","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-8928","kev_date_added":null,"published":"2017-05-14"},{"cvss_score":8.3,"headline":"mailcow-dockerized XSS Vulnerability in Quarantine UI Allows Unauthorized Access and Data Manipulation","id":"CVE-2023-49077","kev_date_added":null,"published":"2023-11-30"}],"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":"2024-08-05","vendors":["mailcow"]},"summary":"An unauthenticated attacker can inject JavaScript into API logs, leading to script execution in the victim's browser, potentially causing data theft or unauthorized actions.","url":"https://insights.sbomify.com/CVE-2024-41959/"}