dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-64235

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in AmentoTech Tuturn allows Path Traversal.This issue affects Tuturn: from n/a before 3.6.

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

Path Traversal vulnerability in AmentoTech Tuturn allows attackers to access files outside the web root directory through specially crafted path inputs. The vulnerability stems from insufficient validation of user-supplied file paths, likely in file upload or file inclusion functionality.

MitigationUpgrade to Tuturn version 3.6 or later. If upgrade is not immediately possible, implement strict input validation using allowlists and normalize all file paths to prevent directory traversal sequences (../).

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify Tuturn installation and version
    Locate the Tuturn application files (typically in web root) and check version.php, composer.json, or package.json for version number. If using a package manager, run 'composer show amentotech/tuturn' or check installed packages.
    Affected if Installed version is earlier than 3.6 (no version specified means all versions before 3.6 are affected)
  2. Locate file upload or file inclusion modules
    Search the codebase for file handling functions: grep for 'move_uploaded_file', 'file_get_contents', 'include', 'require', 'fopen' combined with user input ($_GET, $_POST, $_REQUEST). Focus on modules related to profile pictures, attachments, documents, or any 'include' functionality.
    Affected if File upload or file inclusion functionality exists and processes user-supplied paths without validation
  3. Inspect input validation in file handling code
    Examine the PHP files handling file operations. Look for direct use of user input in file paths without sanitization. Check if $_GET, $_POST, or request parameters are used in file operations like 'include($_REQUEST["file"])' or similar patterns.
    Affected if User-supplied parameters are used in file operations without proper path validation (no realpath(), no basename(), no allowlist)
  4. Check for directory traversal patterns in logs
    Review web server access logs (Apache access.log, Nginx access.log) for suspicious requests containing '../' sequences, such as '?file=../../etc/passwd' or similar path traversal attempts.
    Affected if Logs show successful or attempted path traversal requests targeting the Tuturn application
  5. Test file inclusion endpoint if accessible
    If an endpoint accepts file parameters (e.g., ?page= or ?file=), attempt a safe test: append a known file path outside the web root. Observe if the application returns content from outside the intended directory.
    Affected if The application returns file contents from outside the intended directory when given '../' sequences

The environment is affected if Tuturn version is below 3.6 and file upload/include functionality processes user-supplied paths without strict validation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Tuturn version 3.6 or later. If upgrade is not immediately possible, implement strict input validation using allowlists and normalize all file paths to prevent directory traversal sequences (../).

Recommended fix Moderate confidence

Tuturn version 3.6

  1. 1. Backup your current Tuturn installation and database before proceeding with any upgrade
  2. 2. Download Tuturn version 3.6 or later from the official source (ThemeForest or vendor directly)
  3. 3. Review the release notes for version 3.6 to understand any changes or new features
  4. 4. Upload and install the new version, replacing the existing files
  5. 5. Run any database migrations if required by the upgrade
  6. 6. Verify the installation was successful and test that the path traversal vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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