CVE-2021-44349
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 · uneditedSQL Injection vulnerability exists in TuziCMS v2.0.6 via the id parameter in App\Manage\Controller\DownloadController.class.php.
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 confidenceSQL injection vulnerability in TuziCMS v2.0.6 allows remote attackers to execute arbitrary SQL commands via the unsanitized 'id' parameter in DownloadController.class.php. The vulnerability exists in the download management functionality accessible through the Manage module.
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= 2.0.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm TuziCMS installationLocate the TuziCMS installation directory. Common paths include /var/www/html/, /wwwroot/, or the web server's document root. Look for the main application files and the version file (often version.php, config.php, or similar).Affected if TuziCMS is not installed or the installation directory cannot be found.
-
Verify the installed version is 2.0.6Open the version file or check the admin interface for the exact version number. Compare against the affected version: 2.0.6.Affected if The installed version is exactly 2.0.6.
-
Locate DownloadController.class.phpNavigate to the application source code and find DownloadController.class.php, typically in the application/controllers or module directory. This file handles the download management functionality.Affected if The file exists in the expected location within the TuziCMS installation.
-
Inspect the 'id' parameter handling in DownloadControllerOpen DownloadController.class.php and search for code that processes the 'id' parameter, particularly in methods related to download management. Look for SQL queries that directly use $_GET['id'] or $_POST['id'] without sanitization, prepared statements, or parameter binding.Affected if The 'id' parameter is used in SQL queries without parameterized queries, input validation, or escaping functions.
-
Confirm Manage module accessCheck if the Manage module (admin panel) is accessible and the download management functionality is enabled. Verify the routing or menu configuration that maps to DownloadController.Affected if The Manage module and its download management feature are accessible without additional authentication barriers.
A user is affected if they are running TuziCMS version 2.0.6 with the DownloadController.class.php containing unsanitized 'id' parameter usage in SQL queries and the Manage module's download functionality is accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement prepared statements/parameterized queries for all database operations involving user input, particularly the 'id' parameter in DownloadController. Apply input validation and output encoding as defense-in-depth measures.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2021-44349 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-44349 in production — separate from our analysis above.
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.
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.
- 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