{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103977 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103977 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103977 is a high-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-103977 and fix it if it is affected.\n\nWhat it is: CVE-2026-103977 is a high-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-103977 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-103977/ (Markdown: https://insights.sbomify.com/CVE-2026-103977/index.md)","id":"CVE-2026-103977","markdown":"https://insights.sbomify.com/CVE-2026-103977/index.md","name":"CVE-2026-103977","record":{"aliases":["GHSA-4hfj-6478-5cv7"],"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 with valid primary credentials can bypass TOTP rate limits by resetting sessions, enabling brute-force attacks against two-factor authentication.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-841","name":"Improper Enforcement of Behavioral Workflow"},{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.23.0, FileRise stores failed TOTP verification attempts in $_SESSION. An attacker who already possesses a target account's valid primary credential can restart the login workflow in a new session and restore the second-factor attempt allowance, permitting continued online TOTP guessing beyond the intended five-attempt limit. The pending-login TOTP handlers did not share a durable account-wide limit. This issue is fixed in version 3.23.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-01","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-01T18:48:25Z","kind":"github_poc","ref":"https://github.com/pervinzahidli/CVE-2026-103977","stars":0,"title":"Session-scoped TOTP rate limiting permits repeated verification attempts"}],"tier":"poc_unverified"},"has_fix":false,"headline":"FileRise: Session-scoped TOTP rate limiting permits repeated verification attempts","id":"CVE-2026-103977","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 renameFolder omits destination-parent authorization","id":"CVE-2026-103988"},"packages":[],"prev":{"headline":"Appium: Symlink based Zip Slip in @appium/support ZIP extraction","id":"CVE-2026-103975"},"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["error311"]},"summary":"Attackers with valid primary credentials can bypass TOTP rate limits by resetting sessions, enabling brute-force attacks against two-factor authentication.","url":"https://insights.sbomify.com/CVE-2026-103977/"}