Advisory

GHSA-h6cx-gjxx-v25c

Also known as: CVE-2026-82395

Summary

Sulu: Media move/update authorization bypass (IDOR)

Details

Impact

A media move authorization bypass (IDOR) lets a backend user move a media out of a collection they have no access to.

The media move endpoint resolves its permission check from the collection value in the request rather than from the media's real collection. MediaManager::move() then reassigns the media without re-checking its actual source collection. A user who has edit rights on collection A but no rights on a restricted collection B can move a media that lives in B by naming A in the request. The move succeeds, the media ends up in A, and the user can then view and download content they were never allowed to see.

This only affects installations that use per-collection (object level) permissions to restrict some collections. Exploitation requires an authenticated backend user with edit rights on at least one collection, and knowledge of the target media id.

Patches

Fixed in 2.6.25 and 3.0.8. MediaManager::move() now verifies edit permission on the media's real source collection and on the destination collection before moving it.

Workarounds

If you cannot upgrade immediately:

  • Restrict the media edit permission to trusted users, so untrusted users cannot trigger a move.
  • Apply the fix manually by adding an edit permission check on the media's real source collection (and the destination) inside MediaManager::move().

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-09-02 14:57 UTC
Modified
2026-09-02 15:15 UTC

Affected packages and fixes

sulu/sulu

Packagist · All systems

Affected

  • introduced 0, fixed 2.6.25 (ecosystem)

Fixed versions

2.6.25

Fix

The export has no generic command for this ecosystem.

sulu/sulu

Packagist · All systems

Affected

  • introduced 3.0.0-alpha1, fixed 3.0.8 (ecosystem)

Fixed versions

3.0.8

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences