dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-13699

HIGH · 7.0 CVSS v3.0 Published 2025-12-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges

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 · unedited
MariaDB mariadb-dump Utility Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of MariaDB. Interaction with the mariadb-dump utility is required to exploit this vulnerability but attack vectors may vary depending on the implementation. The specific flaw exists within the handling of view names. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-27000.

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 · moderate confidence

This is a directory traversal vulnerability in mariadb-dump where improper validation of user-supplied view names allows attackers to manipulate file paths during dump operations. The lack of path validation enables writing files to arbitrary locations on the system, leading to code execution in the context of the user running mariadb-dump.

MitigationRestrict access to mariadb-dump to trusted users only, validate all database object names before processing, and apply vendor patches for MariaDB when available. Consider running mariadb-dump in isolated environments with minimal privileges.

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
Local
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify mariadb-dump installation and version
    Run 'mariadb-dump --version' or 'mysqldump --version' to determine the installed version of the MariaDB/MySQL dump utility
    Affected if The installed version falls within the affected range (if known) or is an unpatched version of mariadb-dump
  2. Verify view creation permissions in databases
    Connect to the database and run 'SELECT TABLE_SCHEMA, TABLE_NAME FROM information_schema.VIEWS WHERE DEFINER LIKE "%@%";' to enumerate existing views in the system
    Affected if Any views exist in databases accessible to untrusted users, as these view names could be manipulated for directory traversal
  3. Check user privileges for mariadb-dump execution
    Review which system users have execute permission on the mariadb-dump binary (ls -la /usr/bin/mariadb-dump or similar) and which database users can connect to the server
    Affected if Untrusted or non-admin users have access to execute mariadb-dump against production databases
  4. Inspect database objects for path-like characters in names
    Query the database for view/table names containing '../' or absolute path characters: 'SELECT TABLE_NAME FROM information_schema.TABLES WHERE TABLE_NAME LIKE "../%" OR TABLE_NAME LIKE "/%";
    Affected if Any database objects (views) have names that contain directory traversal sequences or absolute path characters
  5. Review mariadb-dump command execution history
    Check shell history or audit logs for mariadb-dump commands that specify view names or use --views parameter with user-supplied input
    Affected if mariadb-dump is being run with view names that could be externally influenced by untrusted input

A user is affected if they run an unpatched version of mariadb-dump and untrusted users can either execute the tool or manipulate view names during dump operations, allowing path traversal to write files to arbitrary system locations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to mariadb-dump to trusted users only, validate all database object names before processing, and apply vendor patches for MariaDB when available. Consider running mariadb-dump in isolated environments with minimal privileges.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13699 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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