# CVE-2026-54050: Sakai: IDOR in Profile Image Deletion Allows Any Authenticated User to Delete Any User's Profile Image > Authenticated users can delete any other user's profile image or pronunciation recording due to missing ownership checks in the API. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Sep 2026 - **Updated:** 15 Sep 2026 - **Also known as:** GHSA-9284-fjc3-fmmj ## What is CVE-2026-54050? CVE-2026-54050 is a medium-severity missing authorization vulnerability in sakaiproject sakai, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Sakai is a Collaboration and Learning Environment (CLE). From 23.0 until 23.5 and 25.3, the DELETE /api/users/{userId}/profile/image endpoint allows an authenticated user to delete another user's profile image because ProfileController.removeProfileImage() passes the attacker-controlled userId to ProfileServiceImpl.removeProfileImage() without verifying ownership, and profileImageUploadedRepository.deleteById(userId) removes the selected row. The related DELETE /api/users/{userId}/profile/pronunciation endpoint also omits session validation and ownership checks before ProfileServiceImpl.removePronunciationRecording() deletes the target user's recording. The upload path is not affected because it already verifies ownership, and superusers remain intentionally authorized to modify other profiles. Successful exploitation can repeatedly remove profile identity artifacts, including administrator and instructor images, and disrupt workflows that rely on those artifacts. This issue is fixed in versions 23.5, 25.3, and 26.0. Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key) ## Which versions are affected by CVE-2026-54050? 8 open source packages ship an affected version, including org.sakaiproject.profile2:profile2-api and org.sakaiproject.profile2:profile2-impl. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.sakaiproject.profile2:profile2-api` | Maven | From 23.0 | 23.5 | | `org.sakaiproject.profile2:profile2-api` | Maven | From 23.0 | 23.5 | | `org.sakaiproject.profile2:profile2-api` | Maven | From 25.0 to 25.2 | None | | `org.sakaiproject.profile2:profile2-api` | Maven | From 25.0 to 25.2 | None | | `org.sakaiproject.profile2:profile2-impl` | Maven | From 23.0 | 23.5 | | `org.sakaiproject.profile2:profile2-impl` | Maven | From 23.0 | 23.5 | | `org.sakaiproject.profile2:profile2-impl` | Maven | From 25.0 to 25.2 | None | | `org.sakaiproject.profile2:profile2-impl` | Maven | From 25.0 to 25.2 | None | ## How do I fix CVE-2026-54050? Upgrade org.sakaiproject.profile2:profile2-api to 23.5 or later. ## Is CVE-2026-54050 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54050 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-54050 and fix it if it is affected. What it is: CVE-2026-54050 is a medium-severity missing authorization vulnerability in sakaiproject sakai, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54050 exists. Affected packages and fixed versions: - org.sakaiproject.profile2:profile2-api (Maven): affected from 23.0; fixed in 23.5 - org.sakaiproject.profile2:profile2-api (Maven): affected from 23.0; fixed in 23.5 - org.sakaiproject.profile2:profile2-api (Maven): affected from 25.0 up to 25.2; no fix listed - org.sakaiproject.profile2:profile2-api (Maven): affected from 25.0 up to 25.2; no fix listed - org.sakaiproject.profile2:profile2-impl (Maven): affected from 23.0; fixed in 23.5 - org.sakaiproject.profile2:profile2-impl (Maven): affected from 23.0; fixed in 23.5 - org.sakaiproject.profile2:profile2-impl (Maven): affected from 25.0 up to 25.2; no fix listed - org.sakaiproject.profile2:profile2-impl (Maven): affected from 25.0 up to 25.2; no fix listed Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-54050/ (Markdown: https://insights.sbomify.com/CVE-2026-54050/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54050 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54050 - OSV: https://osv.dev/vulnerability/CVE-2026-54050 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-54050/ Summaries are generated and may contain mistakes; the official description above is the record.