Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Sulu: Media move/update authorization bypass (IDOR)

CVE-2026-82395GHSA-h6cx-gjxx-v25c

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (sulu/sulu 3.0.8, 2.6.25), redeploy, then verify what is actually installed.

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

  • Packagist sulu/sulu

    Affected
    <= 2.6.24>= 3.0.0-alpha1, < 3.0.8
    Fixed in
    3.0.8, 2.6.25

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-82395: 0.43% estimated exploitation activity in the next 30 days; percentile 37.05 (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.

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…

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

    Amended from ghsa record GHSA-h6cx-gjxx-v25c

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-h6cx-gjxx-v25c

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-82395

Advisory: Sulu: Media move/update authorization bypass (IDOR)
IDs: CVE-2026-82395, GHSA-h6cx-gjxx-v25c
Record: https://patchnext.com/advisories/cve-2026-82395 (revision 3, source checked 26 Oct 2026, 14:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sulu/sulu 3.0.8, 2.6.25. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist sulu/sulu: affected <= 2.6.24; >= 3.0.0-alpha1, < 3.0.8; fixed in 3.0.8, 2.6.25

## Suggested inspection (read-only)
- Packagist sulu/sulu: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sulu/sulu.
- 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-h6cx-gjxx-v25c (OSV record GHSA-h6cx-gjxx-v25c lists affected ranges: Packagist sulu/sulu >=0 =3.0.0-alpha1 <3.0.8 (fixed))
- Verified: https://github.com/advisories/GHSA-h6cx-gjxx-v25c (GitHub-reviewed advisory GHSA-h6cx-gjxx-v25c lists affected ranges: Packagist sulu/sulu >=0 =3.0.0-alpha1 <3.0.8)

Commands are suggestions: review each one before running it.

Loading voting…