{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33477 exists.","fix":"No fix has been published for CVE-2026-33477 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33477 is a medium-severity missing authorization vulnerability in error311 FileRise, published on 26 Mar 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-33477 and fix it if it is affected.\n\nWhat it is: CVE-2026-33477 is a medium-severity missing authorization vulnerability in error311 FileRise, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33477 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-33477/ (Markdown: https://insights.sbomify.com/CVE-2026-33477/index.md)","id":"CVE-2026-33477","markdown":"https://insights.sbomify.com/CVE-2026-33477/index.md","name":"CVE-2026-33477","record":{"aliases":["GHSA-62wx-vp78-2p83"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"FileRise file manager","requires_auth":"low_privilege","summary":"Authenticated users with read_own permissions can improperly access other users' file content via the snippet API endpoint.","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":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. In versiosn 2.3.7 through 3.10.0, the file snippet endpoint `/api/file/snippet.php` allows an authenticated user with only `read_own` access to a folder to retrieve snippet content from files uploaded by other users in the same folder. This is a server-side authorization flaw in the `read_own` enforcement for hover previews. Version 3.11.0 fixes the issue.","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 has incorrect authorization in /api/file/snippet.php allows read_own users to read other users’ file content","id":"CVE-2026-33477","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":"AVideo Multi-Chain Attack: Unauthenticated Remote Code Execution via Clone Key Disclosure, Database Dump, and Command Injection","id":"CVE-2026-33478"},"packages":[],"prev":{"headline":"SiYuan has an Unauthenticated Arbitrary File Read via Path Traversal","id":"CVE-2026-33476"},"products":["FileRise"],"published":"2026-03-26","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.5,"headline":"FileRise affected by an Unauthenticated File Read Due to Insufficient Access Control","id":"CVE-2026-25231","kev_date_added":null,"published":"2026-02-09"},{"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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-26","vendors":["error311"]},"summary":"Authenticated users with read_own permissions can improperly access other users' file content via the snippet API endpoint.","url":"https://insights.sbomify.com/CVE-2026-33477/"}