APITable up to 1.13.0-beta.1 InternalNotifyController create fromUserId access control

Summaryinfo

A vulnerability classified as problematic has been found in APITable up to 1.13.0-beta.1. Impacted is an unknown function of the file /api/v1/internal/notification/create of the component InternalNotifyController. The manipulation of the argument fromUserId leads to access control. This vulnerability is traded as CVE-2026-80207. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in APITable up to 1.13.0-beta.1. It has been rated as problematic. This issue affects some unknown processing of the file /api/v1/internal/notification/create of the component InternalNotifyController. The manipulation of the argument fromUserId with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is integrity. The summary by CVE is:

APITable through 1.13.0-beta.1 annotates the create handler of InternalNotifyController with requiredLogin = false. ResourceInterceptor honours that annotation by returning before any session or API key is validated, and the nginx gateway shipped with the product proxies every /api request to the backend server, so POST /api/v1/internal/notification/create is reachable by any unauthenticated client that can reach the gateway. An attacker can persist arbitrary notifications in apitable_player_notification against any user ID they name, and because fromUserId can be set to 0 the message is stored with the system sender and renders in the victim's inbox as a legitimate system notification. The body extras content is stored verbatim and forwarded to the frontend.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-80207 since 08/26/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. 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/27/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

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 the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• APITable

Version

• 1.13.0-beta.0
• 1.13.0-beta.1

Website

• Product: https://github.com/apitable/apitable/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion