WPPConnect Server up to 2.10.76 Static Mount missing authentication

Summaryinfo

A vulnerability, which was classified as problematic, was found in WPPConnect Server up to 2.10.76. This impacts an unknown function of the component Static Mount. Such manipulation leads to missing authentication. This vulnerability is traded as CVE-2026-123197. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in WPPConnect Server up to 2.10.76. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Static Mount. The manipulation with an unknown input leads to a missing authentication vulnerability. Using CWE to declare the problem leads to CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Impacted is confidentiality. CVE summarizes:

WPPConnect Server through 2.10.76 contains a missing authentication vulnerability that allows unauthenticated attackers to read decrypted sticker media through the /files static mount. Attackers can enumerate Unix timestamps in GET /files/file<timestamp>.webp requests to retrieve stickers from any session, bypassing per-session token checks.

The advisory is available at github.com. This vulnerability is handled as CVE-2026-123197 since 11/05/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 11/05/2026).

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

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• WPPConnect

Name

• Server

Version

• 2.10.0
• 2.10.1
• 2.10.2
• 2.10.3
• 2.10.4
• 2.10.5
• 2.10.6
• 2.10.7
• 2.10.8
• 2.10.9
• 2.10.10
• 2.10.11
• 2.10.12
• 2.10.13
• 2.10.14
• 2.10.15
• 2.10.16
• 2.10.17
• 2.10.18
• 2.10.19
• 2.10.20
• 2.10.21
• 2.10.22
• 2.10.23
• 2.10.24
• 2.10.25
• 2.10.26
• 2.10.27
• 2.10.28
• 2.10.29
• 2.10.30
• 2.10.31
• 2.10.32
• 2.10.33
• 2.10.34
• 2.10.35
• 2.10.36
• 2.10.37
• 2.10.38
• 2.10.39
• 2.10.40
• 2.10.41
• 2.10.42
• 2.10.43
• 2.10.44
• 2.10.45
• 2.10.46
• 2.10.47
• 2.10.48
• 2.10.49
• 2.10.50
• 2.10.51
• 2.10.52
• 2.10.53
• 2.10.54
• 2.10.55
• 2.10.56
• 2.10.57
• 2.10.58
• 2.10.59
• 2.10.60
• 2.10.61
• 2.10.62
• 2.10.63
• 2.10.64
• 2.10.65
• 2.10.66
• 2.10.67
• 2.10.68
• 2.10.69
• 2.10.70
• 2.10.71
• 2.10.72
• 2.10.73
• 2.10.74
• 2.10.75
• 2.10.76

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion