{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-41807 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41807 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41807 is a high-severity vulnerability in M-Files Server, published on 18 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41807 and fix it if it is affected.\n\nWhat it is: CVE-2021-41807 is a high-severity vulnerability in M-Files Server, published on 18 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-41807 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-41807/ (Markdown: https://insights.sbomify.com/CVE-2021-41807/index.md)","id":"CVE-2021-41807","markdown":"https://insights.sbomify.com/CVE-2021-41807/index.md","name":"CVE-2021-41807","record":{"aliases":["GHSA-5c8j-7c6c-838x"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"M-Files Server","requires_auth":"none","summary":"Attackers can brute-force user accounts due to missing rate limiting in M-Files Server and Web products.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"M-Files Corporation","cpe":[{"product":"m-files_server","vendor":"m-files"},{"product":"m-files_web","vendor":"m-files"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"Lack of rate limiting in M-Files Server and M-Files Web products with versions before 21.12.10873.0 in certain type of user accounts allows unlimited amount of attempts and therefore makes brute-forcing login accounts easier.","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":"Security feature bypass in M-Files Server","id":"CVE-2021-41807","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in M-Files Server","id":"CVE-2021-41808"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2021-41805"},"products":["M-Files Server","M-Files Web"],"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":"Attackers can brute-force user accounts due to missing rate limiting in M-Files Server and Web products.","url":"https://insights.sbomify.com/CVE-2021-41807/"}