NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

CVE-2026-33486 — documents

MEDIUMFix: roadiz/core-bundle-dev-app@7904f69

CVE-2026-33486 is a medium-severity (CVSS 6.8) Server-Side Request Forgery (SSRF) vulnerability in roadiz/documents. A fix is available for roadiz/documents — see the affected versions and patch details below.

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

Also known asGHSA-rc55-58f4-687g
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33486.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk
0.00%0.30%0.60%0.90%0.0%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
🐘roadiz/documents🐘roadiz/documents🐘roadiz/documents🐘roadiz/documents

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

FieldDetails
Vulnerability ClassServer-Side Request Forgery (SSRF) & Local File Inclusion (LFI)
Affected ComponentRZ\Roadiz\Documents\DownloadedFile::fromUrl()
PrerequisitesAuthenticated user with ROLE_ACCESS_DOCUMENTS

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 into the Flysystem Documents storage.

The Flaw

The $url parameter is passed to fopen without any schema validation or sanitization. In PHP, when stream wrappers are enabled, functions like fopen do not restrict operations to HTTP streams. If a file:// scheme is supplied, PHP seamlessly converts the operation into a local file system read. Because an attacker tightly controls the XML feed (e.g., from a Podcast integration), they can inject a file:// URI, forcing the CMS to "download" internal system files directly into the publicly accessible Media Library.


Proof of Concept (PoC)

To reliably reproduce this vulnerability without requiring a live external URL, the attacker simply mimics the behavior of the Podcast importer manipulating the internal system.

Step 1: Craft the Malicious Payload

The attacker creates a standard Podcast RSS XML feed (podcast.xml) and hosts it externally (or on an internal network reachable by the CMS). Inside this XML, the href attribute for the podcast thumbnail is weaponized to target a sensitive system file:

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">
  <channel>
    <title>Roadiz LFI Exploit</title>
    <!-- Payload triggers the local filesystem fetch via PHP streams -->
    <itunes:image href="file:///app/.env" /> 
  </channel>
</rss>

Step 2: Exploit the CMS

  1. Authenticate to the Roadiz Backoffice.
  2. Navigate to Documents (Media Manager).
  3. Select Add a document -> Import from URL (or trigger a Podcast sync).
  4. Supply the URL of the malicious podcast.xml file.

Step 3: Extract the Data

  1. The AbstractPodcastFinder processes the XML and feeds file:///app/.env directly into DownloadedFile::fromUrl().
  2. The Roadiz application silently reads its own .env file, creating a new "Document" arrayed with the contents of the file.
  3. The file manifests in the Media Manager grid as a broken image icon.
  4. The attacker actively downloads the newly generated Document from the dashboard, successfully extracting the framework's internal API keys, database credentials, and APP_SECRET.

Impact Analysis

Exploitation of this vulnerability results in a total loss of Confidentiality for the web application and underlying operating system.

  • Application Compromise: An attacker can retrieve .env, security.yaml, or database .sqlite files, leading to complete horizontal and vertical privilege escalation.
  • System Enumeration: The attacker can read /etc/passwd, enumerating system users in preparation for lateral movement.
  • Cloud Environment Compromise: If deployed within AWS, Azure, or GCP, the SSRF vector can be pivoted to read internal cloud metadata endpoints (e.g., http://169.254.169.254/latest/meta-data/), allowing the attacker to steal Root IAM roles globally compromising the victim's infrastructure.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistroadiz/documents≥ 2.7.0&&< 2.7.92.7.9composer require roadiz/documents:^2.7.9
🐘Packagistroadiz/documents≥ 2.6.0&&< 2.6.282.6.28composer require roadiz/documents:^2.6.28
🐘Packagistroadiz/documents≥ 2.4.0&&< 2.5.442.5.44composer require roadiz/documents:^2.5.44
🐘Packagistroadiz/documentsall versions2.3.42composer require roadiz/documents:^2.3.42

Affected Products

1 product · 4 configurations
Application
core-bundle-dev-approadiz
≥ 2.7.0 && < 2.7.9
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for roadiz/documents, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update roadiz/documents to 2.7.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33486 is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

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 `ROLE_ACCESS_DOCUMENTS` | ## Technical Description The Roadiz backend features tools for imp
O3 Security · Impact-Aware SCA

Is CVE-2026-33486 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2026-33486: documents SSRF — Fixed in 2.7.9