Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

org.sakaiproject.profile2:profile2-api

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5MavenAmendedPublished

    Sakai Profile Image Deletion has an IDOR

    CVE-2026-54050 · GHSA-9284-fjc3-fmmj

    Affected
    • Maven org.sakaiproject.profile2:profile2-api >= 23.0, < 23.5; >= 25.0, <= 25.2
    Fixed in
    23.5· Partial vendor fix
    Issue
    The Sakai REST API endpoint DELETE /api/users/{userId}/profile/image does not verify that the requesting user is authorized to modify the target user's profile. Any authenticated user can delete the profile image of any other user, including administrators, by supplying a different userId in the path. The service layer has no authorization check, and the delete cascades through Content Hosting Service (CHS) with a security advisor that bypasses all CHS permission checks. Details ProfileController.removeProfileImage() in the webapi module retrieves the current user's session but performs no comparison between the authenticated user and the target userId path parameter: ProfileServiceImpl.removeProfileImage() delegates directly to dao.removeProfileImage(userUuid) with no authorization check. The DAO calls profileImageUploadedRepository.deleteById(userId), removing the profileimagest row unconditionally. For contrast, the upload endpoint setProfileImage() correctly verifies…

    Recommended action: Upgrade to 23.5; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →