notionnext-org NotionNext up to 4.10.10 Authentication Guard pages/api/cache.js cleanCache token missing authentication

Summaryinfo

A vulnerability, which was classified as problematic, was found in notionnext-org NotionNext up to 4.10.10. This affects the function cleanCache of the file pages/api/cache.js of the component Authentication Guard. The manipulation of the argument token results in missing authentication. This vulnerability is cataloged as CVE-2026-101004. The attack may be launched remotely. There is no exploit available. Versions 4.1.0 - 4.9.5.2 allow unauthenticated exploitation due to missing method check. In versions 4.9.5.7 - 4.10.10 a guard present but only enforced when CACHE_REVALIDATION_TOKEN is set. Default deployments remain unprotected. The vendor was contacted early about this disclosure but did not respond in any way.

Detailsinfo

A vulnerability was found in notionnext-org NotionNext up to 4.10.10. It has been classified as problematic. Affected is the function cleanCache of the file pages/api/cache.js of the component Authentication Guard. The manipulation of the argument token with an unknown input leads to a missing authentication vulnerability. CWE is classifying the issue as CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. This is going to have an impact on availability.

This vulnerability is traded as CVE-2026-101004. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 09/27/2026).

The vendor was contacted early about this disclosure but did not respond in any way. Versions 4.1.0 - 4.9.5.2 allow unauthenticated exploitation due to missing method check. In versions 4.9.5.7 - 4.10.10 a guard present but only enforced when CACHE_REVALIDATION_TOKEN is set. Default deployments remain unprotected.

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

• notionnext-org

Name

• NotionNext

Version

• 4.10.0
• 4.10.1
• 4.10.2
• 4.10.3
• 4.10.4
• 4.10.5
• 4.10.6
• 4.10.7
• 4.10.8
• 4.10.9
• 4.10.10

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #920379: notionnext-org NotionNext main branch Missing Authentication for Critical Function (CWE-306) (by zyx122126)

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

Discussion