{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105633 exists.","fix":"No fix has been published for CVE-2026-105633 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-105633 is a high-severity missing authorization vulnerability in makeplane plane, published on 5 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-105633 and fix it if it is affected.\n\nWhat it is: CVE-2026-105633 is a high-severity missing authorization vulnerability in makeplane plane, published on 5 Oct 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-105633 exists.\n\nAffected product: makeplane plane. 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-105633/ (Markdown: https://insights.sbomify.com/CVE-2026-105633/index.md)","id":"CVE-2026-105633","markdown":"https://insights.sbomify.com/CVE-2026-105633/index.md","name":"CVE-2026-105633","record":{"aliases":["GHSA-5mxw-g5mw-3v3w"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Plane project management","requires_auth":"low_privilege","summary":"Attackers can hijack attachment ownership by exploiting missing issue_id scope checks in the PATCH endpoint, allowing unauthorized modification of other users' files.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Plane is an open-source project management tool. Prior to 1.4.0, the V2 issue-attachment PATCH endpoint accepts issue_id in the URL but omits it from the database query. A project member can use an issue_id they control in the URL while targeting another user's attachment by its pk UUID. Because the server matches only pk, workspace, and project_id, it modifies the attachment regardless of the issue_id in the URL. When the attachment is pending and has not been confirmed as uploaded, the PATCH handler sets created_by = request.user and transfers attachment ownership to the attacker. This issue is fixed in 1.4.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":"Plane: Issue Attachment Ownership Hijacking via Missing `issue_id` Scope","id":"CVE-2026-105633","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Plane: Privilege Escalation: Project Guest Can Demote Admin/Member Roles","id":"CVE-2026-105634"},"packages":[],"prev":{"headline":"Plane: Broken Access Control - joinProject GraphQL mutation allows self-join into private (secret) projects","id":"CVE-2026-105632"},"products":["plane"],"published":"2026-10-05","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["makeplane"]},"summary":"Attackers can hijack attachment ownership by exploiting missing issue_id scope checks in the PATCH endpoint, allowing unauthorized modification of other users' files.","url":"https://insights.sbomify.com/CVE-2026-105633/"}