{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25231 exists.","fix":"No fix has been published for CVE-2026-25231 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25231 is a high-severity missing authorization vulnerability in error311 FileRise, published on 9 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25231 and fix it if it is affected.\n\nWhat it is: CVE-2026-25231 is a high-severity missing authorization vulnerability in error311 FileRise, published on 9 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25231 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-25231/ (Markdown: https://insights.sbomify.com/CVE-2026-25231/index.md)","id":"CVE-2026-25231","markdown":"https://insights.sbomify.com/CVE-2026-25231/index.md","name":"CVE-2026-25231","record":{"aliases":["GHSA-hv99-77cw-hvpr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Web file manager","requires_auth":"none","summary":"Unauthenticated attackers can read files from the uploads directory in FileRise due to missing access controls, exposing sensitive data.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"filerise","vendor":"filerise"}],"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-552","name":"Files or Directories Accessible to External Parties"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"FileRise is a self-hosted web file manager / WebDAV server. Versions prior to 3.3.0, the application contains an unauthenticated file read vulnerability due to the lack of access control on the /uploads directory. Files uploaded to this directory can be accessed directly by any user who knows or can guess the file path, without requiring authentication. As a result, sensitive data could be exposed, and privacy may be breached. This vulnerability is fixed in 3.3.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-25231.yaml","stars":null,"title":"FileRise \u003c= 3.3.0 - Unauthenticated File Read"}],"tier":"weaponised"},"has_fix":false,"headline":"FileRise affected by an Unauthenticated File Read Due to Insufficient Access Control","id":"CVE-2026-25231","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Gogs has a Protected Branch Deletion Bypass in Web Interface","id":"CVE-2026-25232"},"packages":[],"prev":{"headline":"FileRise affected by HTML Injection using color property in file tags","id":"CVE-2026-25230"},"products":["FileRise"],"published":"2026-02-09","related":[{"cvss_score":8.9,"headline":"FileRise vulnerable to Cross-Site Scripting (XSS) in SVG File Handling","id":"CVE-2025-68116","kev_date_added":null,"published":"2025-12-16"},{"cvss_score":8.2,"headline":"FileRise: Default Encryption Key Enables Token Forgery and Config Decryption","id":"CVE-2026-33072","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.1,"headline":"Path traversal in FileRise","id":"CVE-2026-33329","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.1,"headline":"FileRise improper ownership/permission validation allowed cross-tenant file operations","id":"CVE-2025-62509","kev_date_added":null,"published":"2025-10-20"},{"cvss_score":8.1,"headline":"FileRise insecure folder visibility via name-based mapping and incomplete ACL checks","id":"CVE-2025-62510","kev_date_added":null,"published":"2025-10-20"},{"cvss_score":7.1,"headline":"FileRise ONLYOFFICE integration allows read-only users to overwrite files via forged save callback","id":"CVE-2026-33330","kev_date_added":null,"published":"2026-03-24"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-10","vendors":["error311"]},"summary":"Unauthenticated attackers can read files from the uploads directory in FileRise due to missing access controls, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-25231/"}