Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5amended

Sakai Profile Image Deletion has an IDOR

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

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS
  • CVE-2026-54050: 0.31% estimated exploitation activity in the next 30 days; percentile 24.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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: 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-9284-fjc3-fmmj

  2. Revision 1 · created ·

    Published from osv record GHSA-9284-fjc3-fmmj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54050

Advisory: Sakai Profile Image Deletion has an IDOR
IDs: CVE-2026-54050, GHSA-9284-fjc3-fmmj
Record: https://patchnext.com/advisories/cve-2026-54050 (revision 2, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.sakaiproject.profile2:profile2-api 23.5; org.sakaiproject.profile2:profile2-impl 23.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.sakaiproject.profile2:profile2-api: affected >= 23.0, < 23.5; >= 25.0, <= 25.2; fixed in 23.5
- Maven org.sakaiproject.profile2:profile2-impl: affected >= 23.0, < 23.5; >= 25.0, <= 25.2; fixed in 23.5

## Suggested inspection (read-only)
- Maven org.sakaiproject.profile2:profile2-api: check the installed version with your package manager.
- Maven org.sakaiproject.profile2:profile2-impl: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.sakaiproject.profile2:profile2-api, org.sakaiproject.profile2:profile2-impl.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9284-fjc3-fmmj (OSV record GHSA-9284-fjc3-fmmj lists affected ranges: Maven org.sakaiproject.profile2:profile2-api >=23.0 =25.0 =23.0 =25.0 <=25.2)
- Verified: https://github.com/advisories/GHSA-9284-fjc3-fmmj (GitHub-reviewed advisory GHSA-9284-fjc3-fmmj lists affected ranges: Maven org.sakaiproject.profile2:profile2-api >=23.0 =25.0 =23.0 =25.0 <=25.2)

Commands are suggestions: review each one before running it.

Loading voting…