GHSA-rc55-58f4-687g
MEDIUMRoadiz has Server-Side Request Forgery (SSRF) in roadiz/documents
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
roadiz/documents🐘roadiz/documents🐘roadiz/documents🐘roadiz/documentsReal-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.
| 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 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
- Authenticate to the Roadiz Backoffice.
- Navigate to Documents (Media Manager).
- Select Add a document -> Import from URL (or trigger a Podcast sync).
- Supply the URL of the malicious
podcast.xmlfile.
Step 3: Extract the Data
- The
AbstractPodcastFinderprocesses the XML and feedsfile:///app/.envdirectly intoDownloadedFile::fromUrl(). - The Roadiz application silently reads its own
.envfile, creating a new "Document" arrayed with the contents of the file. - The file manifests in the Media Manager grid as a broken image icon.
- 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.sqlitefiles, 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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | roadiz/documents | ≥ 2.7.0&&< 2.7.9 | 2.7.9 |
| 🐘Packagist | roadiz/documents | ≥ 2.6.0&&< 2.6.28 | 2.6.28 |
| 🐘Packagist | roadiz/documents | ≥ 2.4.0&&< 2.5.44 | 2.5.44 |
| 🐘Packagist | roadiz/documents | all versions | 2.3.42 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for roadiz/documents. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update roadiz/documents to 2.7.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rc55-58f4-687g is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rc55-58f4-687g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-rc55-58f4-687g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-rc55-58f4-687g in your dependencies?
O3 detects GHSA-rc55-58f4-687g across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.