shlinkio Shlink up to 5.1.5 Tag Statistics Endpoint orderBy sql injection

Summaryinfo

A vulnerability was found in shlinkio Shlink up to 5.1.5. It has been rated as critical. Impacted is an unknown function of the component Tag Statistics Endpoint. Performing a manipulation of the argument orderBy results in sql injection. This vulnerability is known as CVE-2026-18737. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in shlinkio Shlink up to 5.1.5. It has been classified as critical. This affects an unknown function of the component Tag Statistics Endpoint. The manipulation of the argument orderBy with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Shlink contains a blind SQL injection vulnerability that allows any authenticated API key holder to inject arbitrary SQL fragments by supplying an unvalidated direction value in the orderBy query parameter of the tag statistics endpoint. Attackers can craft a malicious direction string containing SQL subqueries that flows unsanitized into a Doctrine QueryBuilder ORDER BY clause, enabling time-based, boolean-oracle, and error-based extraction of sensitive data including long URLs, visitor records, IP addresses, geolocation data, user agents, and hashed API key secrets from any tenant.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-18737 since 08/03/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/03/2026). MITRE ATT&CK project uses the attack technique T1505 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-52434). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• shlinkio

Name

• Shlink

Version

• 5.1.0
• 5.1.1
• 5.1.2
• 5.1.3
• 5.1.4
• 5.1.5

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion