<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-20T10:34:28.231933+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-62858</id>
    <title>fkie_cve-2026-62858</title>
    <updated>2026-10-20T10:34:28.252034+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>YOURLS is a self-hosted, customizable URL shortener written in PHP. Prior to 1.10.5, yourls_get_request() extracted the request path without sanitization, after which yourls_sanitize_url() and yourls_esc_url() preserved dot and slash traversal sequences before an attacker-controlled keyword reached file_exists() and include() under YOURLS_PAGEDIR. An unauthenticated remote attacker could traverse outside the intended pages directory and include a local PHP file that was already present on the server, such as an uploaded or injected file, causing the file to execute in the YOURLS web process. This issue is fixed in version 1.10.5.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-62858"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-f8ff-652m-j5rx</id>
    <title>GHSA-f8ff-652m-j5rx — YOURLS: Unauthenticated File Inclusion</title>
    <updated>2026-10-20T10:34:28.252100+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: yourls/yourls</p>
<p>## Summary</p>
<p>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.</p>
<p>## Details</p>
<p>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.</p>
<p>The unsanitized keyword is then directly concatenated into a filesystem path and passed to `file_exists()` and later `include()` operations, enabling path traversal attacks.</p>
<p>**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
```</p>
<p>## Proof of Concept (POC)</p>
<p>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`)</p>
<p>### Setup
Place a test file in web root:</p>
<p>`./test.php`:
```php
&lt;?php
phpinfo();
?&gt;
```
&lt;img width="502" height="126" alt="image" src="https://github.com/user-attachments/assets/14f33f90-625b-4c65-8a…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-f8ff-652m-j5rx"/>
  </entry>
</feed>
