{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104105 exists.","fix":"No fix has been published for CVE-2026-104105 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-104105 is a medium-severity authentication bypass vulnerability in error311 FileRise, published on 14 Oct 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-2026-104105 and fix it if it is affected.\n\nWhat it is: CVE-2026-104105 is a medium-severity authentication bypass vulnerability in error311 FileRise, published on 14 Oct 2026. Any signed-in user can exploit it over the network, 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-2026-104105 exists.\n\nAffected product: error311 FileRise. 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-2026-104105/ (Markdown: https://insights.sbomify.com/CVE-2026-104105/index.md)","id":"CVE-2026-104105","markdown":"https://insights.sbomify.com/CVE-2026-104105/index.md","name":"CVE-2026-104105","record":{"aliases":["GHSA-9pg4-98cx-r82j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"FileRise file manager","requires_auth":"low_privilege","summary":"Attackers can replay captured TOTP codes to bypass two-factor authentication and take over accounts in FileRise.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise verifies that a TOTP code is valid for the accepted time window but does not record that the same account and time step already succeeded. An attacker who has the target account's valid primary credential and captures a TOTP code after its successful use can replay that code from another pending-login session before the window closes. The issue does not by itself disclose the primary credential or TOTP code. This issue is fixed in version 3.23.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"FileRise: TOTP codes are not single-use — valid 6-digit code can be replayed within its window (capture-replay)","id":"CVE-2026-104105","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"FileRise: 2FA disable and TOTP enrollment lack step-up re-authentication; enrollment activates before verification","id":"CVE-2026-104106"},"packages":[],"prev":{"headline":"Ludwig: Path traversal in dataset archive extraction allows arbitrary file write via symlink members","id":"CVE-2026-104103"},"products":["FileRise"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["error311"]},"summary":"Attackers can replay captured TOTP codes to bypass two-factor authentication and take over accounts in FileRise.","url":"https://insights.sbomify.com/CVE-2026-104105/"}