{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33330 exists.","fix":"No fix has been published for CVE-2026-33330 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33330 is a high-severity missing authorization vulnerability in error311 FileRise, published on 24 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-33330 and fix it if it is affected.\n\nWhat it is: CVE-2026-33330 is a high-severity missing authorization vulnerability in error311 FileRise, published on 24 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-33330 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-33330/ (Markdown: https://insights.sbomify.com/CVE-2026-33330/index.md)","id":"CVE-2026-33330","markdown":"https://insights.sbomify.com/CVE-2026-33330/index.md","name":"CVE-2026-33330","record":{"aliases":["GHSA-6c3j-f4x4-36m3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"FileRise web file manager","requires_auth":"low_privilege","summary":"Authenticated read-only users can overwrite files by forging ONLYOFFICE save callbacks, allowing unauthorized data modification.","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.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"FileRise is a self-hosted web file manager / WebDAV server. Prior to version 3.10.0, a broken access control issue in FileRise's ONLYOFFICE integration allows an authenticated user with read-only access to obtain a signed save callbackUrl for a file and then directly forge the ONLYOFFICE save callback to overwrite that file with attacker-controlled content. This issue has been patched in version 3.10.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 ONLYOFFICE integration allows read-only users to overwrite files via forged save callback","id":"CVE-2026-33330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"oRPC: Stored XSS in OpenAPI Reference Plugin via unescaped JSON.stringify","id":"CVE-2026-33331"},"packages":[],"prev":{"headline":"Path traversal in FileRise","id":"CVE-2026-33329"},"products":["FileRise"],"published":"2026-03-24","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"}],"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-24","vendors":["error311"]},"summary":"Authenticated read-only users can overwrite files by forging ONLYOFFICE save callbacks, allowing unauthorized data modification.","url":"https://insights.sbomify.com/CVE-2026-33330/"}