Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-54350 – Unauthenticated NoSQL Operator Injection – Budibase prior to 3.39.12

Be the first to know when new zero-days emerge:

Summary

CVE-2026-54350 is a critical unauthenticated NoSQL operator injection vulnerability in Budibase, the open-source low-code platform, affecting all versions prior to 3.39.12. By injecting JSON metacharacters into published-app query parameters, an unauthenticated attacker can override the builder-defined database filter and read or overwrite every document in the backing collection with a single HTTP request. The vulnerability carries a CVSS v3.1 base score of 10.0 (Critical).

Technical details

  • Root cause: The enrichContext function (packages/server/src/sdk/workspace/queries/queries.ts:121–138) substitutes attacker-controlled parameter values directly into the raw JSON body of a query before calling JSON.parse(). The input validator validateQueryInputs (packages/server/src/api/controllers/query/index.ts:61–71) only rejects Handlebars markers ({{, }}) and does not escape JSON metacharacters (", “, }).
  • Injection mechanism: A parameter value containing a closing quote and additional keys lifts attacker-controlled fields into the parsed filter object. For MongoDB find queries, duplicate-key JSON parsing causes the attacker’s key (e.g., {"$exists": true}) to override the builder’s intended filter, returning every document in the collection. The same primitive against a published updateMany query widens the filter scope to the full collection.
  • Authentication bypass: The authorized middleware (packages/server/src/middleware/authorized.ts:141–148) short-circuits all authentication and CSRF checks when a query’s role is set to PUBLIC. The endpoint POST /api/v2/queries/:queryId requires no session — only the x-budibase-app-id header, which is publicly visible in any published-app URL.
  • Affected datasources: MongoDB, CouchDB, Elasticsearch, DynamoDB-PartiQL, and REST datasources with a JSON body. SQL-backed datasources (PostgreSQL, MySQL, MSSQL, Oracle, MariaDB) are not affected, as they use bind-parameterised interpolation.
  • Impact: Full mass data read (Confidentiality: HIGH) and mass data write/overwrite (Integrity: HIGH) across all vulnerable datasources. Scope is Changed, as the injected query crosses the security boundary into the backing database.

Affected software

  • @budibase/server (npm): all versions prior to 3.39.12

Severity

| Metric | Value |
|—|—|
| CVSS v3.1 Base Score | 10.0 (Critical) |
| Vector String | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N |
| Attack Vector | Network |
| Privileges Required | None |
| User Interaction | None |
| Scope | Changed |

Mitigation and recommended actions

  • Immediate action – patch: Upgrade @budibase/server to version 3.39.12 or later, which contains the vendor-provided fix.
  • If immediate patching is not possible:
    • Restrict public internet access to all Budibase instances via firewall or network policy.
    • Audit published applications and temporarily revoke the PUBLIC role from any non-SQL queries (MongoDB, CouchDB, Elasticsearch, DynamoDB-PartiQL, REST-with-JSON-body) until the patch is applied.
    • Treat all data in collections backing PUBLIC queries as potentially compromised pending a security review.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge