CVE-2026-10706
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Adalo’s no-code app builder, (Versions 1 and 2) the attackers may extract full user records and correlate user behavior across multiple applications via dbId enumeration. The platform does not implement data minimization, privacy by design, or implement appropriate technical safeguards, allowing sensitive information to be exposed to unauthorized parties.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Adalo no-code platform (Versions 1 and 2) allows attackers to enumerate database IDs (dbId) to extract full user records and correlate user behavior across multiple applications. This occurs because the platform lacks data minimization, privacy-by-design principles, and appropriate technical access controls, enabling unauthorized exposure of sensitive user information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Adalo platform is in useInventory your deployed applications and services to identify any using the Adalo no-code platform. Check application metadata, dependencies, or infrastructure configurations for 'Adalo' references.Affected if Adalo no-code platform (version 1 or 2) is deployed in the environment
-
Identify the Adalo versionLocate the version identifier for your Adalo installation through admin console, configuration files, or software bill of materials. Compare against versions 1 and 2.Affected if Running Adalo version 1 or version 2 (any subversion)
-
Inspect database query API endpointsReview API endpoints or internal database query interfaces that accept database IDs (dbId) as parameters. Check if these endpoints are accessible without authentication or proper authorization headers.Affected if Database query endpoints accept dbId parameters and are accessible without valid authentication tokens or session cookies
-
Test for unauthorized ID enumerationUsing a test account or unauthenticated session, attempt to access sequential or predictable dbId values (e.g., dbId 1, 2, 3...) via the API. Observe if each request returns full user records or sensitive personal data without authorization errors.Affected if Sequential dbId enumeration returns user records, profiles, or behavioral data without 403/401 authorization failures
-
Verify cross-application data correlation exposureTest whether different applications' user IDs can be correlated by enumerating dbIds across multiple application contexts, checking if user identity or behavioral data from one application leaks into another.Affected if User records exposed via dbId enumeration contain cross-application identifiers or behavioral data that should be isolated per-application
A user is affected if their Adalo environment (v1 or v2) exposes database query endpoints that allow unauthenticated or unauthorized enumeration of sequential dbId values to retrieve user records.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper access controls, rate limiting, and authentication/authorization checks on database queries to prevent enumeration. Apply privacy-by-design principles including data minimization to restrict the exposure of user records to only authorized parties.
- Consultation12.0 h
- Implementation32.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $19,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10706 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10706 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data