CVE intelligence and bounded remediation

CVE-2026-48821 — Shaarli is a personal bookmarking service

Medium CVSS 5.8

Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a DOM-based Cross-Site Scripting (XSS) vulnerability in the Thumbnail Synchronizer feature. When an administrator runs the thumbnail update process, malicious bookmark titles are returned via an AJAX response and inserted into the DOM using innerHTML without proper sanitization. The issue originates from the interaction between the backend thumbnail update endpoint and the frontend JavaScript responsible for rendering update progress. On the backend, the ThumbnailsController::ajaxUpdate method returns bookmark data formatted using the 'raw' formatter. This includes the unescaped bookmark title in the JSON response. On the client side, the script thumbnails-update.js processes this AJAX response and dynamically updates the progress interface. Administrators using the thumbnail synchronization feature are affected and exploitation could lead to session hijacking, privilege escalation, backdoor injection and full compromise. This issue has been fixed in version 0.16.2.

Severity
Medium
CVSS
5.8 (3.1)
Published
2026-06-17
CISA KEV
Not currently listed
Ecosystem
javascript/npm
Weaknesses
CWE-79

Affected products

No browser-safe affected-product rows are available.

Matched remediation archetype

Cross-site scripting and unsafe browser output

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace reflected, stored, and DOM-derived untrusted values into HTML, attributes, URLs, styles, scripts, and client-side template sinks.
  • Identify affected origins, authenticated user roles, sensitive browser capabilities, and where content is shared across tenants.
  • Review framework escaping, rich-text sanitization, legacy templates, and client-side rendering paths.

Remediate safely

  • Use context-aware framework output encoding and safe DOM APIs; keep untrusted data out of executable contexts.
  • Sanitize intentionally supported markup with a maintained allowlist policy and validate URLs and attributes separately.
  • Update affected rendering components and add tests for every output context using inert sentinel markup.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.