{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-104106 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-104106 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-104106 is a medium-severity vulnerability in error311 FileRise, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-104106 and fix it if it is affected.\n\nWhat it is: CVE-2026-104106 is a medium-severity vulnerability in error311 FileRise, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-104106 in the wild and no public exploit code.\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-104106/ (Markdown: https://insights.sbomify.com/CVE-2026-104106/index.md)","id":"CVE-2026-104106","markdown":"https://insights.sbomify.com/CVE-2026-104106/index.md","name":"CVE-2026-104106","record":{"aliases":["GHSA-77m8-hm3q-mrr5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"FileRise file manager","requires_auth":"low_privilege","summary":"An attacker with an authenticated session can bypass two-factor authentication by disabling or enrolling TOTP without proper re-authentication or verification.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-620","name":"Unverified Password Change"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise permits an authenticated session with a valid CSRF token to disable TOTP without recent full reauthentication or to begin enrollment when the account currently has no TOTP secret. The enrollment endpoint returns 409 rather than directly overwriting an already configured secret, but it persists and activates a newly generated secret before a TOTP code verifies possession. An attacker controlling an existing authenticated session can therefore disable an existing second factor or enroll one after the account has no configured secret; this is not a direct overwrite of an active authenticator. 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":"none_known"},"has_fix":false,"headline":"FileRise: 2FA disable and TOTP enrollment lack step-up re-authentication; enrollment activates before verification","id":"CVE-2026-104106","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"FileRise: Authenticated path traversal escapes configured storage root through inherited ACLs","id":"CVE-2026-104107"},"packages":[],"prev":{"headline":"FileRise: TOTP codes are not single-use — valid 6-digit code can be replayed within its window (capture-replay)","id":"CVE-2026-104105"},"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["error311"]},"summary":"An attacker with an authenticated session can bypass two-factor authentication by disabling or enrolling TOTP without proper re-authentication or verification.","url":"https://insights.sbomify.com/CVE-2026-104106/"}