TadtoolsApplication · Tadtools Project

CVE-2021-41566

CRITICAL · 9.8 CVSS v3.1 Published 2021-10-08
Fix available
A fix is available. Upgrade to 3.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The file extension of the TadTools file upload function fails to filter, thus remote attackers can upload any types of files and execute arbitrary code without logging in.

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

TadTools contains a file upload function that lacks proper file extension filtering, allowing unauthenticated remote attackers to upload arbitrary file types including executable scripts. This enables remote code execution on the affected server.

MitigationImplement strict file extension whitelisting, disable script execution in upload directories, and ensure authentication is required for all file upload functionality.

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
TadtoolsApplication
Affected:< 3.2.2

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. Identify Tadtools installation
    Locate the Tadtools installation directory and look for files such as class/TadtoolsUpload.php, tadtools.php, or similar core Tadtools files
    Affected if Tadtools is present on the system
  2. Determine installed version
    Check version information in the project's composer.json, package.json, or version file (often in the root directory or in a README file)
    Affected if Installed version is lower than 3.2.2
  3. Verify file upload module is present
    Look for upload-related PHP files or modules in the Tadtools directory, such as files containing 'upload' in the filename
    Affected if The file upload module exists and is accessible via the web server
  4. Check if upload endpoint is accessible without authentication
    Attempt to access the file upload functionality directly via HTTP without providing any login credentials
    Affected if The upload endpoint responds without requiring authentication
  5. Inspect file extension validation
    Examine the upload handling code (e.g., in TadtoolsUpload.php or similar) to see if there is any file extension filtering in place
    Affected if No extension filtering exists, or filtering allows executable extensions such as .php, .phtml, .exe, .sh, or .js

The system is affected if Tadtools versions below 3.2.2 are installed with the file upload module exposed and accessible without authentication, and no extension filtering is implemented.

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
Upgrade available Upgrade to 3.2.2 or later
Fixed in 3.2.2
Interim mitigation

Implement strict file extension whitelisting, disable script execution in upload directories, and ensure authentication is required for all file upload functionality.

Recommended fix High confidence

3.2.2

  1. 1. Back up the current TadTools installation and database before proceeding
  2. 2. Download TadTools version 3.2.2 from the official source (tadtools website or the project's distribution channel)
  3. 3. Replace the existing TadTools files with the new version 3.2.2
  4. 4. Verify that the file upload function now properly filters file extensions and blocks executable file types
  5. 5. Test that legitimate file uploads still work correctly for allowed file types

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

Fix this in Tadtools Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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