CVE-2022-30018: Mobotix Control Center (MxCC) through 2.5.4.5 has Insufficiently Protected Credentials, Storing Passwords in a

Q: How do I fix CVE-2022-30018?

mxcontrolcenter: upgrade to newer than 2.5.4.5. Exact commands for each OS are on this page.

Q: Is CVE-2022-30018 being exploited?

CVE-2022-30018 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-2022-30018 affect?

CVE-2022-30018 affects mxcontrolcenter. Severity is high (CVSS 8.8). Mobotix Control Center (MxCC) through 2.5.4.5 has Insufficiently Protected Credentials, Storing Passwords in a Recoverable Format via the MxCC.ini config file. The credential storage method in this software enables an attacker/user of the m

Q: How urgent is CVE-2022-30018?

Priority 52/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2022-30018 is a high-severity flaw (CVSS 8.8) affecting mxcontrolcenter. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Mobotix Control Center (MxCC) through 2.5.4.5 has Insufficiently Protected Credentials, Storing Passwords in a Recoverable Format via the MxCC.ini config file. The credential storage method in this software enables an attacker/user of the machine to gain admin access to the software and gain access to recordings/recording locations.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-522
Published	2022-05-19
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: mobotix

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

Am I affected?

Timeline

2022-05-19 14:15 UTCPublished CVE record published
2026-06-17 04:42 UTCUpdated Record last modified

mobotix mxcontrolcenter UPGRADE

Affected: <= 2.5.4.5

Fixed in: newer than 2.5.4.5

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 2.5.4.5 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mxcontrolcenter

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-2022-30018?

mxcontrolcenter: upgrade to newer than 2.5.4.5. Exact commands for each OS are on this page.

Is CVE-2022-30018 being exploited?

CVE-2022-30018 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-2022-30018 affect?

CVE-2022-30018 affects mxcontrolcenter. Severity is high (CVSS 8.8). Mobotix Control Center (MxCC) through 2.5.4.5 has Insufficiently Protected Credentials, Storing Passwords in a Recoverable Format via the MxCC.ini config file. The credential storage method in this software enables an attacker/user of the m

How urgent is CVE-2022-30018?

Priority 52/100. High severity; Public exploit reference

References

← Back to latest CVEs