S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Mar 25, 2026

CVE-2026-31816 Scanner

CVE-2026-31816 Scanner - Authentication Bypass vulnerability in Budibase

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.1k
Times Used
continuous scan runs
5.8k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2026-31816
9.1
CVSScritical
Exploitable remotely over the internet · no authentication required.

Budibase is a low code platform for creating internal tools, workflows, and admin panels. In 3.31.4 and earlier, the Budibase server's authorized() middleware that protects every server-side API endpoint can be completely bypassed by appending a webhook path pattern to the query string of any request. The isWebhookEndpoint() function uses an unanchored regex that tests against ctx.request.url, which in Koa includes the full URL with query parameters. When the regex matches, the authorized() middleware immediately calls return next(), skipping all authentication, authorization, role checks, and CSRF protection. This means a completely unauthenticated, remote attacker can access any server-side API endpoint by simply appending ?/webhooks/trigger (or any webhook pattern variant) to the URL.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
budibaseby Budibase
<= 3.31.4
Updated Aug 22, 2026View on NVD →
Detail

Budibase is an open-source low-code platform used by developers to create internal business applications rapidly. Companies often deploy Budibase to improve processes, internal operations, or create custom tools without extensive coding knowledge. Its versatility allows usage across various industries, whether for managing employee records, project tracking, or data management. Companies rely on its capability to integrate with various data sources and existing technology infrastructures. The platform is built to accelerate the development cycle and reduce overhead by offering pre-built modules and templates. Its prominence in the business sector makes safe deployment critical, especially concerning security vulnerabilities.

The identified vulnerability in Budibase is an authentication bypass that affects versions up to and including 3.31.4. It stems from an unanchored regex in the middleware that governs webhook path patterns, allowing unauthorized access to server-side API endpoints. This vulnerability lets unauthenticated users interact with APIs intended to be protected from unauthorized access. Exploiting this gap, attackers can engage with the system without proper authorization, posing significant risks to the data integrity and security on servers using these Budibase versions. Such vulnerabilities typically arise from logic flaws during software development, underscoring the importance of rigorous coding standards and security audits.

Technical details reveal that the authentication bypass occurs within the authorized() middleware, where unanchored regex matching fails to secure webhook paths correctly. Attackers can craft a request that includes webhook patterns within the URL, enabling unauthorized API access. This flaw effectively disables authentication checks intended to protect sensitive operations, leading to potential data exposure or manipulation. The endpoint verified through HTTP requests responds positively with code 200 if the crafted exploit is successful, confirming the bypass. Therefore, resolving this requires code patches that anchor regex checks correctly and verify access permissively.

Exploitation of this authentication bypass might lead to unauthorized data exposure or system manipulation. Malicious entities can bypass security measures and access functionalities or data reserved for authenticated users. This can include unauthorized data retrieval, data modification, or unauthorized actions performed on the server, jeopardizing data integrity and confidentiality. Such exposure could lead to further compromise of the host system or its associated networks, depending on the nature of data handled by the compromised APIs.

REFERENCES

Solution Advice
  • Upgrade Budibase to a version newer than 3.31.4 or apply the latest available patch ensuring the authentication routines are secured.
  • Regularly review your API endpoint routes and authentication regex patterns to ensure they are correctly anchored and tested.
  • Deploy additional monitoring to detect anomalous API utilization patterns, hinting at unauthorized use.
  • Implement least-privilege principles to restrict access levels across API operations, further mitigating unauthorized access risks.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.