yourls/yourls
Affected
- introduced
0, fixed1.10.5(ecosystem)
Fixed versions
1.10.5
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: 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 (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 Execution
Proof 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();
?>
<img width="502" height="126" alt="image" src="https://github.com/user-attachments/assets/14f33f90-625b-4c65-8abf-244af2385f68" />
Attack Request
GET /../../test HTTP/1.1
Host: target.com
Connection: close
Response (Apache Environment)
<img width="1704" height="614" alt="image" src="https://github.com/user-attachments/assets/8750a3c0-a96c-4896-a087-d7b5cfeccd30" />
Impact
Medium Basis: The source's own band: MODERATE
0, fixed 1.10.5 (ecosystem)1.10.5
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0