Stored XSS via raw bookmark title
Published Aug 20, 2026 · Updated Aug 20, 2026
Stored XSS in Shaarli before 0.16.3 allows remote attackers to execute script in visitors' browsers via a crafted bookmark title. In application/front/controller/visitor/BookmarkListController.php, the permalink handler copies bookmark title data into the pagetitle template variable, and the RainTPL includes template emits that value inside the document title without HTML escaping, so a closing title tag and script payload execute in the Shaarli origin. Exploitation requires getting an administrator to save a bookmark with an attacker-controlled title, including by bookmarking an attacker-hosted page whose remote title is imported verbatim, after which visits to /shaare/{hash} run the stored payload and can expose the administrator session.
Summary
What happened
Stored XSS in Shaarli before 0.16.3 allows remote attackers to execute script in visitors' browsers via a crafted bookmark title. In application/front/controller/visitor/BookmarkListController.php, the permalink handler copies bookmark title data into the pagetitle template variable, and the RainTPL includes template emits that value inside the document title without HTML escaping, so a closing title tag and script payload execute in the Shaarli origin. Exploitation requires getting an administrator to save a bookmark with an attacker-controlled title, including by bookmarking an attacker-hosted page whose remote title is imported verbatim, after which visits to /shaare/{hash} run the stored payload and can expose the administrator session.
The record
- CVE
- CVE-2026-50190
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- Shaarli
- Product
- Shaarli
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.16.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory proof of concept for permalink stored XSSproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo