Path TraversalWeakness · CWE-22

CVE-2025-25685

HIGH · 7.5 CVSS v3.1 Published 2025-03-17

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

An issue was discovered in GL-INet Beryl AX GL-MT3000 v4.7.0. Attackers are able to download arbitrary files from the device's file system via adding symbolic links on an external drive used as a samba share.

Technical summary

dbcve analysis · moderate confidence

The GL-MT3000 device with firmware v4.7.0 allows attackers to download arbitrary files from the filesystem by placing symbolic links on an external USB drive configured as a Samba share. The Samba service does not properly validate or restrict symbolic link traversal, allowing directory escape beyond the intended share boundaries.

MitigationDisable Samba share functionality on the external drive if not required, or implement strict symbolic link validation and path restrictions within the Samba configuration to prevent traversal outside the designated share directory.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

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

Identify device model

Check the device model is GL-MT3000. This can be done via web UI under System > Overview or via command line using 'cat /proc/cpuinfo' or 'ubus call system board'.

Affected if Device model is not GL-MT3000, this CVE does not apply.
Check firmware version

Verify the firmware version is v4.7.0. Access the web UI under System > Overview or run 'cat /etc/os-release' or 'fw_printenv' to confirm the installed version.

Affected if Firmware version is not v4.7.0, the specific vulnerability as described may not be present.
Verify Samba service is enabled

Check if the Samba service is running. Run 'ps | grep smbd' or check via web UI under Network Sharing > Samba. Also verify configuration file /etc/samba/smb.conf exists.

Affected if Samba service is not enabled or no Samba configuration exists, the attack vector is not present.
Confirm external USB storage is configured as Samba share

Check the Samba configuration at /etc/samba/smb.conf for shares pointing to USB mount points (typically /mnt or /media). In the web UI, verify if an external USB drive has been added as a Samba share under Network Sharing.

Affected if No external USB drive is configured as a Samba share, the specific traversal vulnerability cannot be exploited.
Check Samba symbolic link security settings

Examine /etc/samba/smb.conf for 'follow symlinks' or 'wide links' settings. Run 'testparm -s /etc/samba/smb.conf 2>/dev/null' to validate the Samba configuration. Look for whether symlink traversal restrictions are disabled or not explicitly set.

Affected if Wide links are enabled or follow symlinks is set to yes without proper ' veto files' rules blocking symlink traversal, the directory escape vulnerability exists.

The environment is affected only if it is a GL-MT3000 device running firmware v4.7.0 with an external USB drive configured as an accessible Samba share where symbolic link restrictions are not properly enforced.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Disable Samba share functionality on the external drive if not required, or implement strict symbolic link validation and path restrictions within the Samba configuration to prevent traversal outside the designated share directory.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

15.0 hours of engineering $2,640

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-25685 — 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

Primary sources

medium.com
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-25685?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.5%

Remediation

A high-priority fix

Have this fixed 15 hrs · Moderate

Typical engagement from $2,640

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-25685 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References