Connected Mobile ExperiencesApplication · Cisco
CVE-2021-1144
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 · uneditedA vulnerability in Cisco Connected Mobile Experiences (CMX) could allow a remote, authenticated attacker without administrative privileges to alter the password of any user on an affected system. The vulnerability is due to incorrect handling of authorization checks for changing a password. An authenticated attacker without administrative privileges could exploit this vulnerability by sending a modified HTTP request to an affected device. A successful exploit could allow the attacker to alter the passwords of any user on the system, including an administrative user, and then impersonate that user.
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 confidenceCisco CMX contains an authorization bypass vulnerability where authenticated users without administrative privileges can modify passwords of any user on the system, including administrative accounts. The flaw resides in the password change functionality which fails to properly validate authorization level before allowing password modifications via modified HTTP requests.
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
Connected Mobile ExperiencesApplication
= 10.6.0= 10.6.1= 10.6.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Cisco CMX installation and versionLocate the Cisco CMX installation and determine its exact version number. This is typically available via the web administration interface (usually at /admin) or via CLI commands such as 'show version' or 'show system info' on the CMX appliance.Affected if The installed version is 10.6.0, 10.6.1, or 10.6.2
-
Verify non-administrative user accounts existLog in to the Cisco CMX web interface or check the user database to confirm that there is at least one authenticated user without administrative privileges.Affected if Non-admin user accounts are present in the system
-
Confirm password change functionality is accessibleAccess the password change or user management section of the Cisco CMX web interface while logged in as a non-administrative user. Attempt to navigate to endpoints or forms that allow password modifications for other users.Affected if The password change functionality is accessible to authenticated users without admin rights
-
Test authorization bypass on password modificationUsing a non-administrative user session, attempt to modify the password of another user (including an administrator account) by intercepting and modifying the HTTP request parameters to target a different user account.Affected if A non-admin user can successfully change another user's password, including administrative accounts
The environment is affected if Cisco CMX version 10.6.0, 10.6.1, or 10.6.2 is running and authenticated non-administrative users can modify passwords of other users through the password change functionality without proper authorization validation.
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 dataApply the relevant Cisco security patch for CVE-2021-1144 or upgrade to a patched version of Cisco CMX. Verify that non-administrative users cannot modify other users' passwords after remediation.
Fix this in Connected Mobile Experiences
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1144 — 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-1144 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