CVE-2021-32953
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 · uneditedAn attacker could utilize SQL commands to create a new user MDT AutoSave versions prior to v6.02.06 and update the user’s permissions, granting the attacker the ability to login.
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 confidenceMDT AutoSave versions prior to v6.02.06 contain a SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL commands. Attackers can create new user accounts and modify user permissions, effectively gaining authenticated access to the application.
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< 6.02.06>= 7.00, <= 7.04< 4.01= 5.00CVSS 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.
-
Identify installed MDT AutoSave versionLocate the MDT AutoSave installation and check the version information, typically found in the application About section, installation directory, or registry entries under the Auvesy product keyAffected if The version number is less than 6.02.06, or falls between 7.00 and 7.04 inclusive, or is 5.00 (for System Platform variant), or less than 4.01 (for System Platform variant)
-
Check if application interface is network-accessibleVerify whether the MDT AutoSave web interface or API endpoint is exposed to network access beyond the internal trusted networkAffected if The application interface is reachable from untrusted networks or the internet, making the unauthenticated SQL injection accessible to remote attackers
-
Inspect database for unauthorized user accountsQuery the application database (typically SQL Server or similar) for user account tables and examine creation dates, especially accounts created around times of suspicious activity or without corresponding administrative recordsAffected if There are user accounts in the database that were created unexpectedly, especially with elevated permissions, or that cannot be traced to legitimate administrative actions
Your environment is affected if MDT AutoSave version falls within the vulnerable ranges AND the application interface is network-accessible, or if unexpected user accounts exist in the database.
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.
dbcve · scoped4.016.02.06
Upgrade MDT AutoSave to version 6.02.06 or later. If immediate patching is not possible, restrict network access to the application interface and monitor for unauthorized account creation in the database.
Autosave: 6.02.06 or 7.04.01+ | Autosave For System Platform: 4.01 or 5.01+
- 1. Identify the currently installed Autosave or Autosave For System Platform version
- 2. For Autosave versions < 6.02.06: Upgrade to version 6.02.06 or later
- 3. For Autosave versions 7.00-7.04: Upgrade to version 7.04.01 or later
- 4. For Autosave For System Platform versions < 4.01: Upgrade to version 4.01 or later
- 5. For Autosave For System Platform version 5.00: Upgrade to version 5.01 or later
- 6. After upgrade, verify the SQL injection vulnerability is remediated by reviewing vendor release notes
- 7. Change any credentials that may have been compromised and implement least-privilege database access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2021-32953 — 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-32953 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