Server: Budibase: NoSQL injection in MongoDB integration: collection dump, $where JS exec, cross-collection pivot, arbitrary update/delete
Budibase server versions up to 3.38.1 contain a NoSQL injection vulnerability in the MongoDB integration. This flaw allows BASIC app users to bypass query-level access controls intended to restrict data visibility per user. The vulnerability arises because user input is handlebars-enriched into MongoDB query JSON with no escaping, then parsed and executed without sanitization. Attackers can inject MongoDB operators to manipulate queries and retrieve or modify unauthorized documents.
AI Analysis
Technical Summary
Budibase's MongoDB datasource integration improperly processes user-supplied parameters by enriching query JSON with Handlebars using no escaping, then parsing it with JSON.parse. This allows injection of MongoDB operators that override intended per-user filters. The injected query reaches MongoDB's find operation unchanged, enabling BASIC users to bypass access controls and read or modify all documents accessible by the connection. Unlike SQL datasources, the MongoDB path lacks parameterization, making it vulnerable to NoSQL injection. A duplicate-key JSON trick enables attackers to craft filters that match all documents, demonstrated in Budibase 3.35.8 with MongoDB 6.
Potential Impact
An attacker with BASIC user privileges can bypass the builder's per-user query filters and access all documents in the MongoDB datasource, potentially exposing sensitive data. The injection also allows arbitrary update or delete operations, compromising data integrity. The vulnerability leads to a confidentiality breach (full data read access) and partial integrity impact (arbitrary updates/deletes). Availability is not affected. The severity is high due to the broad data exposure and privilege bypass.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using MongoDB datasources with untrusted user input in Budibase or restrict BASIC user permissions. Builders should not rely on handlebars-enriched JSON with no escaping for query filtering. Consider implementing server-side query parameterization or input validation to prevent injection. Monitor vendor channels for patches or official fixes.
Server: Budibase: NoSQL injection in MongoDB integration: collection dump, $where JS exec, cross-collection pivot, arbitrary update/delete
Description
Budibase server versions up to 3.38.1 contain a NoSQL injection vulnerability in the MongoDB integration. This flaw allows BASIC app users to bypass query-level access controls intended to restrict data visibility per user. The vulnerability arises because user input is handlebars-enriched into MongoDB query JSON with no escaping, then parsed and executed without sanitization. Attackers can inject MongoDB operators to manipulate queries and retrieve or modify unauthorized documents.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Budibase's MongoDB datasource integration improperly processes user-supplied parameters by enriching query JSON with Handlebars using no escaping, then parsing it with JSON.parse. This allows injection of MongoDB operators that override intended per-user filters. The injected query reaches MongoDB's find operation unchanged, enabling BASIC users to bypass access controls and read or modify all documents accessible by the connection. Unlike SQL datasources, the MongoDB path lacks parameterization, making it vulnerable to NoSQL injection. A duplicate-key JSON trick enables attackers to craft filters that match all documents, demonstrated in Budibase 3.35.8 with MongoDB 6.
Potential Impact
An attacker with BASIC user privileges can bypass the builder's per-user query filters and access all documents in the MongoDB datasource, potentially exposing sensitive data. The injection also allows arbitrary update or delete operations, compromising data integrity. The vulnerability leads to a confidentiality breach (full data read access) and partial integrity impact (arbitrary updates/deletes). Availability is not affected. The severity is high due to the broad data exposure and privilege bypass.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using MongoDB datasources with untrusted user input in Budibase or restrict BASIC user permissions. Builders should not rely on handlebars-enriched JSON with no escaping for query filtering. Consider implementing server-side query parameterization or input validation to prevent injection. Monitor vendor channels for patches or official fixes.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-pmpg-2mxq-6xwr
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6542259c2644c7f8089d10
Added to database: 07/25/2026, 23:09:25 UTC
Last enriched: 07/25/2026, 23:53:26 UTC
Last updated: 07/26/2026, 05:36:03 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.