dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-48822

MEDIUM · 5.8 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Shaarli is a personal bookmarking service. Versions 0.16.1 and prior contain a stored Cross-Site Scripting (XSS) vulnerability in the Markdown-to-HTML conversion process used in the Bookmark Description field. An authenticated user can inject a malicious javascript: URI inside a Markdown link. The vulnerability originates in the filterProtocols method within BookmarkMarkdownFormatter.php.This method attempts to sanitize Markdown links by filtering dangerous protocols (such as javascript:) before rendering. It uses the following regular expression: (#]\((.*?)\)#is). This regex is designed to detect inline Markdown links, but it fails to detect Markdown reference-style links because reference-style links are resolved by the Markdown parser after preprocessing. The filterProtocols method never inspects the actual URL used in these references and as a result, an attacker can supply a javascript: URI inside a reference definition. This issue has been fixed in version 0.16.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Shaarli versions 0.16.1 and prior contain a stored XSS vulnerability in the Markdown-to-HTML conversion for Bookmark Descriptions. The filterProtocols method uses a regex that only detects inline Markdown links but fails to sanitize reference-style links, allowing attackers to inject malicious javascript: URIs that execute after Markdown parsing.

MitigationUpgrade to Shaarli version 0.16.2 or later, which contains the patched filterProtocols method that properly sanitizes both inline and reference-style Markdown links.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Shaarli version
    Check the installed Shaarli version number (typically displayed in the application footer or in a version file within the Shaarli installation directory)
    Affected if Version is 0.16.1 or prior
  2. Verify Markdown description support
    Check if bookmark descriptions accept Markdown input. Look for a description field when creating or editing bookmarks that renders Markdown syntax
    Affected if Markdown descriptions are enabled and users can input custom descriptions
  3. Inspect filterProtocols method
    Locate the filterProtocols method in the Shaarli source code (typically in a link handling or sanitization module). Examine the regex pattern used to detect and sanitize Markdown links
    Affected if The regex only handles inline Markdown links [text](url) and does not include logic for reference-style links [text][ref] with [ref]: url definitions
  4. Search for reference-style Markdown links
    Examine stored bookmark descriptions in the database or export for reference-style Markdown syntax patterns such as [label][reference] paired with [reference]: URL definitions
    Affected if Reference-style links with javascript: or other dangerous URIs are present in stored bookmark descriptions

A user is affected if running Shaarli 0.16.1 or prior where the filterProtocols method fails to sanitize reference-style Markdown links containing javascript: URIs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Shaarli version 0.16.2 or later, which contains the patched filterProtocols method that properly sanitizes both inline and reference-style Markdown links.

Recommended fix High confidence

0.16.2

  1. Backup your current Shaarli installation and database before proceeding
  2. Download Shaarli version 0.16.2 from the official GitHub repository
  3. Replace the existing Shaarli files with the files from version 0.16.2, preserving your configuration and data
  4. Verify that the upgrade was successful by logging in and testing the bookmark description field
  5. Confirm the filterProtocols method in BookmarkMarkdownFormatter.php has been updated to handle reference-style links properly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48822 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48822 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data