How severe is CVE-2017-15363?

CVE-2017-15363 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-15363?

CVE-2017-15363 affects the following packages: aoe/restler (Packagist), luracast/restler (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-15363?

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.

How do I detect CVE-2017-15363 in my Packagist dependencies?

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.

How do I mitigate CVE-2017-15363 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2017-15363 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-15363 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-15363?

CVE-2017-15363 has an EPSS (Exploit Prediction Scoring System) score of 15.3%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2017-15363?

CVE-2017-15363 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2017-15363?

A Nuclei detection template exists for CVE-2017-15363, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2017-15363 published, and has it been updated?

CVE-2017-15363 was published on October 15, 2017 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2017-15363 — restler

HIGH

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

Also known asGHSA-rvmg-xc29-rvxf

Published

Oct 15, 2017

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

15.3%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

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

2 pkgs affected

🐘aoe/restler🐘luracast/restler

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

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

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`aoe/restler`	all versions	1.7.1`composer require aoe/restler:^1.7.1`
🐘Packagist	`luracast/restler`	all versions	3.1.0`composer require luracast/restler:^3.1.0`

Affected Products

1 product · 2 configurations

Application

restlerluracast

< 3.0.0

range

Detection & mitigation playbook

Open-source dependency

Detect
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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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

O3 Security · Impact-Aware SCA

Is CVE-2017-15363 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

Weaponization

Timeline

Disclosed

Oct 15, 2017

Last updated

Oct 24, 2026

Identifiers

CVE-2017-15363

GHSA-rvmg-xc29-rvxf

References

Advisoryextensions.typo3.org · zip Advisoryextensions.typo3.org · restler Advisorynvd.nist.gov · CVE 2017 15363 Webextensions.typo3.org · restler Webgithub.com · 1.7.1 Packagegithub.com · TYPO3 Restler

Related vulnerabilities

This CVE is high severity; 4 of 8 other CVEs with CWE-22 are rated as high or higher (top: critical).

CVE-2026-62331GHSA-4xm8-rg9h-jhq2CVE-2026-9083CVE-2026-115908CVE-2026-118667CVE-2026-118654CVE-2026-116673GHSA-7w82-6f9j-v9jpBrowse all CWE-22

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2017-15363 — restler

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2017-15363

Frequently Asked Questions

Is CVE-2017-15363 in your dependencies?