Baserow up to 2.3.2 Inactive Non-Staff User serializers.py BaserowImpersonateAuthTokenSerializer improper authorization ⚔ [Disputed]

Summaryinfo

A vulnerability was found in Baserow up to 2.3.2 and classified as problematic. This affects the function BaserowImpersonateAuthTokenSerializer of the file backend/src/baserow/api/admin/users/serializers.py of the component Inactive Non-Staff User Handler. Executing a manipulation can lead to improper authorization. This vulnerability is handled as CVE-2026-18817. The attack can be executed remotely. There is not any exploit available. There are still doubts about whether this vulnerability truly exists. It is suggested to upgrade the affected component. The project maintainer explains: "While the problem exists, I'm not really sure if it's a vulnerability. (....) Even though the back gives a token for a deactivate user, none of the endpoints actually work. That said, we will fix it, but so far it seems more like a bug instead of a vulnerability."

Detailsinfo

A vulnerability has been found in Baserow up to 2.3.2 and classified as problematic. This vulnerability affects the function BaserowImpersonateAuthTokenSerializer of the file backend/src/baserow/api/admin/users/serializers.py of the component Inactive Non-Staff User Handler. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect integrity.

This vulnerability was named CVE-2026-18817. The exploitation appears to be difficult. The attack can be initiated remotely. The exploitation needs additional levels of successful authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1548.002.

The real existence of this vulnerability is still doubted at the moment. The project maintainer explains: "While the problem exists, I'm not really sure if it's a vulnerability. (....) Even though the back gives a token for a deactivate user, none of the endpoints actually work. That said, we will fix it, but so far it seems more like a bug instead of a vulnerability."

Upgrading to version 2.3.3 eliminates this vulnerability. The upgrade is hosted for download at github.com.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

• Baserow

Version

• 2.3.0
• 2.3.1
• 2.3.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #857942: baserow c34eb053be98bc0d04fcbf9b2d6b305cba0d5647 CWE-285 Improper Authorization (by GalaxynX)

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion