CVE-2026-82394: Sulu: Fix authorization bypass when creating preview links
Impact A missing authorization check on the preview link endpoint lets a backend user create a public, unauthenticated preview URL for content they are not allowed to see. PreviewLinkController (and the underlying PreviewLinkManager::generate() / revoke()) never enforced a permission on the target resource.
Published Sep 2, 2026
Affected packages
sulu/sulu
- Ecosystem
- Composer (PHP)
- Affected
- <= 2.6.24
- Fixed in
- 2.6.25
- Check
composer show sulu/sulu
sulu/sulu
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.0.0-alpha1, < 3.0.8
- Fixed in
- 3.0.8
- Check
composer show sulu/sulu
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A missing authorization check on the preview link endpoint lets a backend user create a public, unauthenticated preview URL for content they are not allowed to see.
PreviewLinkController (and the underlying PreviewLinkManager::generate() / revoke()) never enforced a permission on the target resource. Any authenticated administration user could call the generate action for any page, article or snippet, including content in a webspace or area they have no VIEW rights on. The endpoint returns a public render URL that resolves the content solely by an opaque token, so the attacker (or anyone they share the link with) can then read the restricted content without authentication.
This affects installations that use Sulu role and webspace permissions to restrict who may see certain content. Exploitation requires an authenticated backend user and the id of the target resource.
Patches
Fixed in 2.6.x and 3.0.x. PreviewLinkManager::generate() and revoke() now resolve the resource's security context and enforce a VIEW permission check before a preview link is created or removed. A user without VIEW access on the resource receives a 403 response and no link is created.
Note on scope: this patch closes the authorization bypass. Two related hardening items from the original report are tracked as a separate follow-up because they require a database migration:
- The preview link token is derived from
substr(md5(uuid), 0, 12)(about 48 bits of entropy). - Preview links never expire.
Workarounds
If you cannot upgrade immediately:
- Restrict backend access so that only trusted users can reach the administration interface.
- Apply the fix manually by adding a VIEW permission check (via
SecurityCheckerInterfaceand the resource's security context) insidePreviewLinkManager::generate()andrevoke().
References
- https://github.com/sulu/sulu/security/advisories/GHSA-65cv-w493-7vhq
- https://nvd.nist.gov/vuln/detail/CVE-2026-82394
- https://github.com/sulu/sulu/commit/44d8844c3514a70b769ab791b9530df806240fab
- https://github.com/sulu/sulu/releases/tag/2.6.25
- https://github.com/sulu/sulu/releases/tag/3.0.8
- https://github.com/advisories/GHSA-65cv-w493-7vhq
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-92692
Sulu: JCR-SQL2 injection via `categories` query parameter (unauthenticated)
medium6.9Sep 23, 2026CVE-2026-82395
Sulu: Media move/update authorization bypass (IDOR)
medium5.3Sep 2, 2026CVE-2026-82396
Sulu: Stored XSS via media download inline-disposition override
medium5.4Sep 2, 2026CVE-2026-45701
Sulu: Weak Cryptographical usage for API Key generation and Reset Tokens
medium6.9May 18, 2026GHSA-9m6v-8fxc-4r44
Sulu: Used API Keys may be available via Admin API
low2.3May 18, 2026CVE-2026-34372
Sulu checks fix permissions for subentities endpoints
medium5.3Mar 30, 2026
