Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.8

Roadiz has Server-Side Request Forgery (SSRF) in roadiz/documents

CVE-2026-33486GHSA-rc55-58f4-687g

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (roadiz/documents 2.7.9, 2.6.28, 2.5.44, 2.3.42), 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 roadiz/documents

    Affected
    >= 2.7.0, < 2.7.9>= 2.6.0, < 2.6.28>= 2.4.0, < 2.5.44< 2.3.42
    Fixed in
    2.3.42, 2.5.44, 2.6.28, 2.7.9

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
EPSS
  • CVE-2026-33486: 0.40% estimated exploitation activity in the next 30 days; percentile 34.04 (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.

This vulnerability allows an authenticated attacker to read any file on the server's local file system that the web server process has access to, including highly sensitive environment variables, database credentials, and internal configuration files. | Field | Details | | :--- | :--- | | Vulnerability Class | Server-Side Request Forgery (SSRF) & Local File Inclusion (LFI) | | Affected Component | RZ\Roadiz\Documents\DownloadedFile::fromUrl() | | Prerequisites | Authenticated user with ROLEACCESSDOCUMENTS | Technical Description The Roadiz backend features tools for importing external media, such as compiling cover art from Podcast RSS Feeds or OEmbed providers. This feature is handled by various MediaFinders, which ultimately pass the extracted media URLs to the DownloadedFile::fromUrl(string $url) parsing mechanism. Inside fromUrl(), the application uses PHP's native fopen() function to fetch the remote resource and copy it into the local temporary directory before injecting it…

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

    Published from ghsa record GHSA-rc55-58f4-687g

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

Advisory: Roadiz has Server-Side Request Forgery (SSRF) in roadiz/documents
IDs: CVE-2026-33486, GHSA-rc55-58f4-687g
Record: https://patchnext.com/advisories/cve-2026-33486 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: roadiz/documents 2.7.9, 2.6.28, 2.5.44, 2.3.42. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist roadiz/documents: affected >= 2.7.0, < 2.7.9; >= 2.6.0, < 2.6.28; >= 2.4.0, < 2.5.44; < 2.3.42; fixed in 2.3.42, 2.5.44, 2.6.28, 2.7.9

## Suggested inspection (read-only)
- Packagist roadiz/documents: 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 roadiz/documents.
- 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://github.com/advisories/GHSA-rc55-58f4-687g (GitHub-reviewed advisory GHSA-rc55-58f4-687g lists affected ranges: Packagist roadiz/documents >=2.7.0 =2.6.0 =2.4.0 =0 <2.3.42)

Commands are suggestions: review each one before running it.

Loading voting…