nday
CVE-2026-48823 GHSA-68qr-fvv8-6mc6

Shaarli has Stored Cross-Site Scripting (XSS) via Tags Search

shaarli / Shaarli

Fecha de divulgación: . nday aún no tiene constancia de una corrección; eso no significa que no exista parche. Ninguna de las cuatro fuentes de PoC la recoge. No figura en el KEV de CISA.

tags weakness typeXSS accesslocal
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

XSS
CWE-79, stated by the CNA GitHub_M y NVD, republishing [email protected]
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N (CVSS 3.1) from the CNA GitHub_M
etapa
DIS
divulgación
cvss
4.8 MEDIUM v3.1

Ciclo de vida

Eje x en UTC; punto = minuto exacto, barra ancha = solo fecha, hueco = desconocida o inferida.
fecha desconocida
DISdivulgada
06-17T20:06Z
PATparcheada
sin registro aún
ANAanalizada
sin registro aún
POCPoC
sin registro aún
ITWexplotada
sin registro aún
KEVen KEV
sin registro aún

Descripción

Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a stored Cross-Site Scripting (XSS) vulnerability in the tag filtering functionality of Shaarli. An authenticated user can inject arbitrary JavaScript into the tags field when creating a bookmark (Shaare). The malicious payload is stored and later executed when users interact with the "Filter by tag" search feature on the homepage. User-supplied input in the tags field is not properly sanitized or output-escaped before being rendered in the tag filtering interface. When a bookmark is created with a malicious payload inside the tag field, the payload is stored in the database. Later, when a user searches using the "Filter by tag" functionality on the homepage, the application renders matching tags dynamically. If the tag value contains HTML with JavaScript event handlers, it is injected into the DOM. This impacts anyone interacting with the "Filter by tag" search functionality, administrators and privileged users. This issue has been fixed in version 0.16.2.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:H
High: administrative or similar privileges
User interaction UI:R
Required: a user must do something, such as open a file or click a link

CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N

CVSS 3.1 vector from the CVE record, scored by the CNA GitHub_M.

Registro de eventos

+DISdivulgación

GitHub_M publicó el registro CVE. CVSS 4.8, severidad media. La evaluación SSVC de CISA asigna a la explotación el valor poc.

fuente cvelist · nday , importación masiva · en bruto
{
  "id": 428273,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-48823",
  "occurred_at": "2026-06-17T20:06:05.616Z",
  "observed_at": "2026-11-13T05:39:52.052485Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:N",
      "version": "3.1",
      "base_score": 4.8,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2026-06-18T12:56:46.297724Z",
      "automatable": "no",
      "exploitation": "poc",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2026-06-17T20:06:05.616Z",
    "assigner_short_name": "GitHub_M"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Debate de investigadores

0 investigadores lo mencionaron en los últimos 7 días

Publicaciones en X de investigadores de la lista de nday que mencionan este CVE, tal como se publicaron. nday no las verifica.

nday aún no ha recopilado publicaciones en X de investigadores de su lista sobre este CVE.

Discussion

0 comments

No comments yet.