File ThingieApplication · Leefish

CVE-2019-25471

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to after 2.5.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
FileThingie 2.5.7 contains an arbitrary file upload vulnerability that allows attackers to upload malicious files by sending ZIP archives through the ft2.php endpoint. Attackers can upload ZIP files containing PHP shells, use the unzip functionality to extract them into accessible directories, and execute arbitrary commands through the extracted PHP files.

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 confidence

FileThingie 2.5.7 has an arbitrary file upload vulnerability in the ft2.php endpoint that allows unauthenticated attackers to upload ZIP archives containing malicious PHP files. The application unpacks these archives into accessible web directories without proper validation, enabling remote code execution.

MitigationDisable PHP execution in upload directories, implement strict file type and content validation before extraction, restrict extraction paths to prevent directory traversal, and consider disabling the unzip functionality or adding authentication.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
File ThingieApplication
Affected:<= 2.5.7

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm File Thingie installation
    Locate ft2.php in the web root or check for files containing 'File Thingie' branding in the application directory structure
    Affected if ft2.php exists and responds to HTTP requests
  2. Identify installed version
    Open ft2.php in a text editor and search for version strings (e.g., '2.5.7', '$version') in the source code, or check for a changelog or readme file
    Affected if The version is 2.5.7 or lower (or no version is displayed, suggesting an older unpatched release)
  3. Verify unzip functionality is present
    Check the ft2.php source code for unzip-related functions (such as 'unzip', 'ZipArchive', or 'extract') and confirm the upload form accepts ZIP file types
    Affected if Unzip code is present and ZIP upload functionality is enabled in the application
  4. Check PHP execution in upload directories
    Examine the web server configuration (Apache .htaccess, Nginx config) and upload directory for PHP execution permissions; look for 'SetHandler' or 'php_flag' directives that restrict PHP execution
    Affected if PHP execution is allowed in the directories where uploads are stored (typically a 'files' or 'uploads' subdirectory)
  5. Confirm authentication status
    Review ft2.php for session validation, login checks, or authentication includes at the beginning of the script; attempt to access ft2.php without credentials
    Affected if No authentication check is performed before allowing file uploads, or authentication can be bypassed

A user is affected if File Thingie version 2.5.7 or lower is installed, the ft2.php upload endpoint is accessible, and PHP execution is permitted in the upload directory.

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
Upgrade available Upgrade to a release after 2.5.7
Interim mitigation

Disable PHP execution in upload directories, implement strict file type and content validation before extraction, restrict extraction paths to prevent directory traversal, and consider disabling the unzip functionality or adding authentication.

Fix this in File Thingie Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-25471 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-25471 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