{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41808 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41808 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41808 is a low-severity vulnerability in M-Files Server, published on 18 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-41808 and fix it if it is affected.\n\nWhat it is: CVE-2021-41808 is a low-severity vulnerability in M-Files Server, published on 18 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-41808 in the wild and no public exploit code.\n\nAffected product: M-Files Server. 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-41808/ (Markdown: https://insights.sbomify.com/CVE-2021-41808/index.md)","id":"CVE-2021-41808","markdown":"https://insights.sbomify.com/CVE-2021-41808/index.md","name":"CVE-2021-41808","record":{"aliases":["GHSA-h62q-wxxr-4qqj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"M-Files Server","requires_auth":"high_privilege","summary":"Enabling federated authentication logging in M-Files Server exposes sensitive information in event logs, requiring configuration changes to mitigate.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"M-Files Corporation","cpe":[{"product":"m-files_server","vendor":"m-files"}],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"In M-Files Server product with versions before 21.11.10775.0, enabling logging of Federated authentication to event log wrote sensitive information to log. Mitigating factors are logging is disabled by default.","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":"Information disclosure in M-Files Server","id":"CVE-2021-41808","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"SSRF vulnerability in M-Files Server products with versions before 22.1.11017.1, allows requests from server.","id":"CVE-2021-41809"},"packages":[],"prev":{"headline":"Security feature bypass in M-Files Server","id":"CVE-2021-41807"},"products":["M-Files Server"],"published":"2022-01-18","related":[{"cvss_score":9.2,"headline":"Support for authentication bypass condition in M-Files LDAP authentication","id":"CVE-2024-10127","kev_date_added":null,"published":"2024-11-20"},{"cvss_score":8.4,"headline":"Path traversal in M-Files API","id":"CVE-2025-5964","kev_date_added":null,"published":"2025-06-15"},{"cvss_score":8.4,"headline":"Path traversal in M-Files API","id":"CVE-2024-6789","kev_date_added":null,"published":"2024-08-27"},{"cvss_score":7.5,"headline":"Denial of service condition in M-Files Server","id":"CVE-2024-4056","kev_date_added":null,"published":"2024-04-26"},{"cvss_score":7.5,"headline":"Brute force vulnerability in M-Files user authentication","id":"CVE-2023-6912","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":7.5,"headline":"Denial of service condition in M-Files Server","id":"CVE-2023-3405","kev_date_added":null,"published":"2023-06-27"},{"cvss_score":7.5,"headline":"Uncontrolled Resource Consuption in M-Files Server","id":"CVE-2023-0383","kev_date_added":null,"published":"2023-04-20"}],"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-02-23","vendors":["M-Files"]},"summary":"Enabling federated authentication logging in M-Files Server exposes sensitive information in event logs, requiring configuration changes to mitigate.","url":"https://insights.sbomify.com/CVE-2021-41808/"}