CVE-2021-32953: An attacker could utilize SQL commands to create a new user MDT AutoSave versions prior to v6.02.06 and update

Q: How do I fix CVE-2021-32953?

autosave: upgrade to 6.02.06; autosave for system platform: upgrade to 4.01. Exact commands for each OS are on this page.

Q: Is CVE-2021-32953 being exploited?

CVE-2021-32953 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2021-32953 affect?

CVE-2021-32953 affects autosave, autosave for system platform. Severity is critical (CVSS 9.8). An 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.

Q: How urgent is CVE-2021-32953?

Priority 56/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADEUPGRADE

CVE-2021-32953 is a critical-severity flaw (CVSS 9.8) affecting autosave, autosave for system platform. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An 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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 31%)
CISA exploited list	No
Weakness	CWE-89
Published	2022-04-01
Last modified	2026-06-17

Publisher (CNA): ICS-CERT · Vendor: auvesy-mdt

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-04-01 23:15 UTCPublished CVE record published
2026-06-17 03:53 UTCUpdated Record last modified

auvesy-mdt autosave UPGRADE

Affected: < 6.02.06 · >= 7.00 and <= 7.04

Fixed in: 6.02.06

Safe to downgrade to: a release before 7.00

1. Check installed version

apt-cache policy autosave || rpm -q autosave || autosave --version

2. UPGRADE to 6.02.06 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade autosave

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade autosave

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 7.00 (Debian / Ubuntu)

apt-cache madison autosave sudo apt install autosave=<VERSION_BEFORE_7.00> sudo apt-mark hold autosave

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list autosave sudo dnf downgrade autosave-<VERSION_BEFORE_7.00> sudo dnf versionlock add autosave

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

auvesy-mdt autosave for system platform UPGRADE

Affected: < 4.01 · 5.00

Fixed in: 4.01

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy autosave-for-system-platform || rpm -q autosave-for-system-platform || autosave-for-system-platform --version

2. UPGRADE to 4.01 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade autosave-for-system-platform

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade autosave-for-system-platform

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-32953?

autosave: upgrade to 6.02.06; autosave for system platform: upgrade to 4.01. Exact commands for each OS are on this page.

Is CVE-2021-32953 being exploited?

CVE-2021-32953 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-32953 affect?

CVE-2021-32953 affects autosave, autosave for system platform. Severity is critical (CVSS 9.8). An 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.

How urgent is CVE-2021-32953?

Priority 56/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2021-32961 HIGH 7.5 UPGRADE UPGRADE A getfile function in MDT AutoSave versions prior to v6.02.06 enables a user to supply an optional parameter,
CVE-2021-32957 HIGH 7.5 UPGRADE UPGRADE A function in MDT AutoSave versions prior to v6.02.06 is used to retrieve system information for a specific pr
CVE-2021-32949 HIGH 7.5 UPGRADE UPGRADE An attacker could utilize a function in MDT AutoSave versions prior to v6.02.06 that permits changing a design
CVE-2021-32945 HIGH 7.5 UPGRADE UPGRADE An attacker could decipher the encryption and gain access to MDT AutoSave versions prior to v6.02.06.
CVE-2021-32937 HIGH 7.5 UPGRADE UPGRADE An attacker can gain knowledge of a session temporary working folder where the getfile and putfile commands ar

References

← Back to latest CVEs