CVE-2026-62858: YOURLS: Unauthenticated File Inclusion
Summary YOURLS versions ≤1.10.4 contain an unauthenticated path traversal vulnerability that allows attackers to include and execute arbitrary PHP files on the server without any credentials. Details The vulnerability exists because YOURLS uses URL sanitization functions (yourlssanitizeurl(), yourlsescurl()) to filter request paths, but these functions are designed to clean URLs, not filesystem paths.
Published Oct 15, 2026
Affected packages
yourls/yourls
- Ecosystem
- Composer (PHP)
- Affected
- <= 1.10.4
- Fixed in
- 1.10.5
- Check
composer show yourls/yourls
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
YOURLS versions ≤1.10.4 contain an unauthenticated path traversal vulnerability that allows attackers to include and execute arbitrary PHP files on the server without any credentials.
Details
The vulnerability exists because YOURLS uses URL sanitization functions (yourls_sanitize_url(), yourls_esc_url()) to filter request paths, but these functions are designed to clean URLs, not filesystem paths. They preserve / and . characters, allowing ../ sequences to pass through unfiltered.
The unsanitized keyword is then directly concatenated into a filesystem path and passed to file_exists() and later include() operations, enabling path traversal attacks.
Data Flow:
HTTP Request URI (with ../)
↓
yourls_get_request() (no sanitization)
↓
yourls_sanitize_url() (preserves / and .)
↓
yourls_esc_url() (permits / and . via regex)
↓
Keyword extraction (preserves ../)
↓
file_exists(YOURLS_PAGEDIR . "/$keyword.php") ← Sink
↓
include(YOURLS_PAGEDIR . "/$keyword.php") ← Code ExecutionProof of Concept (POC)
In the concept validation, we assume that the attacker has uploaded a test.php file to the web root directory, but it cannot be accessed directly. (Of course, it could also be any path, such as /tmp/test.php)
Setup
Place a test file in web root:
./test.php:
<?php
phpinfo();
?>Attack Request
GET /../../test HTTP/1.1
Host: target.com
Connection: closeResponse (Apache Environment)
Impact
- Remote execution of uploaded PHP files – An attacker uploads a malicious PHP file to an arbitrary location on the server (e.g., via another vulnerability or file upload feature), obtains its absolute path but cannot access it directly. The attacker then leverages this vulnerability to include and execute the PHP file, gaining code execution privileges.
- Indirect triggering of PHP code injection – If a PHP code injection point exists on the system (e.g., log injection, session injection) but the injected file cannot be accessed directly due to configuration restrictions, the attacker can use this vulnerability to include and execute the injected code, achieving remote command execution or further compromise.
Credited to web-hacker-team, ozh, dgw, LeoColomb.
References
- https://github.com/YOURLS/YOURLS/security/advisories/GHSA-f8ff-652m-j5rx
- https://nvd.nist.gov/vuln/detail/CVE-2026-62858
- https://github.com/YOURLS/YOURLS/pull/4142
- https://github.com/YOURLS/YOURLS/commit/4e85972160a96e03a419a442d5bd8f21f2f02ddb
- https://github.com/YOURLS/YOURLS/releases/tag/1.10.5
- https://github.com/advisories/GHSA-f8ff-652m-j5rx
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
