CVE-2025-71392
highpriority · track · 32EPSS 0.004 · 38 %ileEUUSEPSS · scored 2026-10-28
SurrealDB before 2.0.5, 2.1.x before 2.1.5, and 2.2.x before 2.2.2 fails to properly escape table and field names in the command-line export command. An authenticated System User with OWNER or EDITOR roles can create tables or fields with malicious names containing SurrealQL. When a higher-privileged user subsequently imports the exported backup, the injected SurrealQL executes, enabling privilege escalation and root-level takeover of the SurrealDB instance. Applications that let users define custom tables or fields are also exposed to a universal second-order SurrealQL injection even when query parameters are sanitized.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · high–critical · 7.6–9.4
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (9)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-ccj3-5p93-8p42SurrealDB server-takeover via SurrealQL injection on backup import2025-04-11ghsa · osvUS
The SurrealDB command-line tool allows exporting databases through the `export` command. It was discovered that table or field names are not properly sanitized in exports, leading to a SurrealQL injection when the backup is reimported. For the injection to occur, an authenticated System User with `OWNER` or `EDITOR` roles needs to create tables or fields with malicious names containing SurrealQL, subsequently exported using the `export` operation The attacker could achieve a privilege escalation and root level access to the SurrealDB instance if a higher privileged user subsequently performs the `import` operation. Furthermore, applications using SurrealDB that allow its users to define custom fields or tables are at risk of a universal second order SurrealQL injection, even if query parameters are properly sanitized. This issue was discovered and patched during an code audit and penetration test of SurrealDB by cure53, the severity defined within cure53's preliminary finding is Critical, matched by our CVSS v4 assessment. ### Impact This attack can be used to perform privilege escalation and complete takeover (root access) of the SurrealDB instance, as well as being able to perform SurrealQL injection attacks against co-tenanted applications where SurrealDB is used as a shared backend for multiple applications. ### Patches A patch has been created that addresses the issue by fixing the bugs in the exporter which failed to escape some characters properly. - Versions 2.0.5, 2.1.5, 2.2.2 and later are not affected by this issue. ### Workarounds For SurrealDB users that are unable to upgrade, users that are looking to perform `import` operations must manually inspect the exported data for injected statements, prior to importing. ### Resources [SurrealDB Documentation - Export](https://surrealdb.com/docs/surrealdb/cli/export) [SurrealDB Documentation - Import](https://surrealdb.com/docs/surrealdb/cli/import) [SurrealDB Documentation - Authentication](https://surrealdb.com/docs/surrealdb/security/authentication)
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (6)
External citations — patches, advisories, analysis.
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-ccj3-5p93-8p42cnnvd
- https://www.vulncheck.com/advisories/surrealdb-before-surrealql-injection-via-exportcnnvd
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-ccj3-5p93-8p42enisa_euvd
- https://www.vulncheck.com/advisories/surrealdb-before-surrealql-injection-via-exportenisa_euvd
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-ccj3-5p93-8p42Vendor Advisorynvd
- https://www.vulncheck.com/advisories/surrealdb-before-surrealql-injection-via-exportThird Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan