CVE-2017-15363 — aoe/restler
HIGHCVE-2017-15363 is a high-severity (CVSS 7.5) Path Traversal vulnerability in aoe/restler. EPSS puts its 30-day exploitation probability at 15.3% (97th percentile). A fix is available for aoe/restler — see the affected versions and patch details below.
Luracast Restler directory traversal vulnerability
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.
How urgent is this, really
CVE-2017-15363 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
aoe/restler🐘luracast/restlerReal-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
Directory traversal vulnerability in public/examples/resources/getsource.php in Luracast Restler through 3.0.0, as used in the restler extension before 1.7.1 for TYPO3, allows remote attackers to read arbitrary files via the file parameter.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | aoe/restler | all versions | 1.7.1composer require aoe/restler:^1.7.1 |
| 🐘Packagist | luracast/restler | all versions | 3.1.0composer require luracast/restler:^3.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aoe/restler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aoe/restler to 1.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-15363 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2017-15363 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2017-15363. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect CVE-2017-15363
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2017-15363 -u https://target- Template
- Luracast Restler 3.0.1 via TYPO3 Restler 1.7.1 - Local File Inclusion
- Severity
- high
- Impact
- The vulnerability allows an attacker to include local files, potentially leading to unauthorized access or code execution.
- Remediation
- Update to the latest version of Restler and TYPO3 to fix the vulnerability.
Template by ProjectDiscovery nuclei-templates (0x_Akoko), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2017-15363 in your dependencies?
O3 Security finds CVE-2017-15363 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.