CVE-2026-41660
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 · uneditedAdmidio is an open-source user management solution. Prior to version 5.0.9, a logic error in Admidio's two-factor authentication reset inverts the authorization check. Non-admin users cannot remove their own TOTP configuration, but they can remove other users' TOTP, including administrators. A group leader with profile edit rights on an admin account can strip that admin's 2FA. This issue has been patched in version 5.0.9.
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 confidenceAdmidio prior to 5.0.9 contains a logic error in the two-factor authentication reset functionality where the authorization check is inverted. Non-admin users, including group leaders with profile edit rights, can remove other users' TOTP configurations (including administrators) but cannot remove their own, enabling privilege escalation through 2FA stripping.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
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 Admidio installation versionLocate the Admidio installation directory and identify the installed version number from version files, configuration, or database recordsAffected if Installed version is prior to 5.0.9 (versions 5.0.0 through 5.0.8 are affected)
-
Verify TOTP two-factor authentication is activeCheck the Admidio system configuration or database to determine if TOTP/2FA functionality has been enabled for the organizationAffected if TOTP two-factor authentication is enabled in the system
-
Identify users with profile edit permissionsReview the Admidio role and permission assignments to find non-administrator users, especially group leaders, who have profile editing capabilitiesAffected if Non-admin users or group leaders possess profile edit rights
Environment is affected if Admidio version is below 5.0.9, TOTP/2FA is enabled, and any non-admin users (including group leaders) have profile edit permissions, allowing them to strip other users' two-factor authentication.
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 · scopedUpgrade to Admidio version 5.0.9 or later. Until patched, monitor user activity for unauthorized TOTP modifications and restrict profile edit permissions to trusted administrators only.
5.0.9
- Backup your Admidio installation and database before upgrading
- Download Admidio version 5.0.9 from the official source (e.g., GitHub releases or admidio.org)
- Follow the standard upgrade procedure for Admidio (refer to official upgrade documentation for your specific deployment method)
- Verify the two-factor authentication reset functionality works correctly after upgrade
- Test that users can only modify their own TOTP settings and not those of other users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41660 — 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-2026-41660 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