CVE-2026-105263
Deferred Deferred - Pending Action

Server-Side Request Forgery in Shaarli

Vulnerability report for CVE-2026-105263, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-05

Last updated on: 2026-10-05

Assigner: VulDB

Description

A security flaw has been discovered in Shaarli up to 0.16.3. The affected element is the function MetadataController of the file application/front/controller/admin/MetadataController.php of the component Admin Metadata Endpoint. Performing a manipulation of the argument url results in server-side request forgery. The attack may be initiated remotely. Upgrading to version 0.16.4 is sufficient to fix this issue. The patch is named 8ca4de8e7c932a684481f5fbb1229fe16de1f4d2. It is advisable to upgrade the affected component.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-05
Last Modified
2026-10-05
Generated
2026-10-05
AI Q&A
2026-10-05
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
shaarli shaarli to 0.16.3 (inc)
shaarli shaarli 0.16.4

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Server-Side Request Forgery (SSRF) vulnerability in Shaarli versions up to 0.16.3. It exists in the /admin/metadata endpoint which fetches remote URLs server-side to extract metadata. The flaw allows attackers to manipulate the URL parameter to access internal services, private networks, or cloud metadata endpoints through the vulnerable server.

Detection Guidance

To detect this vulnerability, check if your Shaarli instance is running a version prior to 0.16.4. Use commands like 'curl -s https://your-shaarli-instance.com/ | grep "Shaarli"' to identify the version. Inspect server logs for unusual requests to the /admin/metadata endpoint or unexpected outbound connections from the server.

Impact Analysis

An attacker could exploit this to use your Shaarli server as a proxy to access internal systems like admin dashboards, CI servers, or secrets managers. They could extract sensitive metadata or access restricted services. The attack requires authentication unless security.open_shaarli is enabled.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, potentially violating GDPR's data protection requirements or HIPAA's security rules for protected health information. The unauthorized server access may result in data breaches requiring regulatory notification.

Mitigation Strategies

Immediately upgrade Shaarli to version 0.16.4 or later. Disable the /admin/metadata endpoint if not needed. Ensure CSRF tokens are enforced and restrict outbound connections from the server to prevent SSRF attacks. Review server logs for signs of exploitation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-105263. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart