dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-41658

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Admidio is an open-source user management solution. Prior to version 5.0.9, the Admidio inventory module enforces authorization for destructive operations (delete, retire, reinstate) only in the UI layer by conditionally rendering buttons. The backend POST handlers at modules/inventory.php for item_delete, item_retire, item_reinstate, item_picture_upload, item_picture_save, and item_picture_delete perform CSRF validation but never check whether the requesting user is an inventory administrator. Any authenticated user who can access the inventory module can permanently delete any inventory item and all its associated data. 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 confidence

Admidio inventory module has a broken access control vulnerability where backend POST handlers (item_delete, item_retire, item_reinstate, item_picture_upload, item_picture_save, item_picture_delete) in modules/inventory.php perform CSRF validation but skip authorization checks for inventory administrator role. Any authenticated user with module access can permanently delete any inventory item.

MitigationUpgrade to Admidio version 5.0.9 or later, which includes proper authorization checks in the backend. Verify that role-based access controls are correctly configured for the inventory module.

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Admidio installation and version
    Check for the presence of Admidio files (e.g., index.php, version.php) in your web root or check the admidio version through the application's about page or version.php file
    Affected if Admidio version is present and is lower than 5.0.9 (the fixed version)
  2. Confirm inventory module is enabled
    Check if the inventory module is active in Admidio by reviewing the module configuration or checking for modules/inventory.php in the installation directory
    Affected if The inventory module (modules/inventory.php) exists and is accessible/enabled in the application
  3. Verify user role configuration for inventory
    Review the role-based access control settings for the inventory module in Admidio's administration panel under Roles or module-specific permissions
    Affected if Non-administrator users or roles have been granted access to the inventory module without proper restrictions
  4. Test for authorization bypass
    As an authenticated user with only basic inventory module access (non-administrator), attempt to send a POST request to the inventory.php handlers (item_delete, item_retire, etc.) targeting an item owned by another user to observe if the action succeeds
    Affected if The action completes successfully without returning an authorization error, indicating the missing authorization check is present

A user is affected if they run Admidio with an inventory module enabled and the installed version is below 5.0.9, allowing any authenticated user with module access to perform administrative actions on inventory items.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Admidio version 5.0.9 or later, which includes proper authorization checks in the backend. Verify that role-based access controls are correctly configured for the inventory module.

Recommended fix High confidence

Admidio version 5.0.9

  1. 1. Identify the Admidio installation directory on your server
  2. 2. Backup both the Admidio database and all application files before proceeding with any changes
  3. 3. Check the current installed version (typically via the admin dashboard or version file in the installation)
  4. 4. Download Admidio version 5.0.9 from the official repository or distribution source
  5. 5. Replace the existing application files with the new version 5.0.9 files, preserving any local configuration files if required
  6. 6. Run any database migration scripts included in the 5.0.9 release if applicable
  7. 7. Verify the upgrade was successful by confirming the new version number in the admin interface
  8. 8. Log in as a non-administrative user with access to the inventory module and confirm authorization controls are now properly enforced on delete, retire, reinstate, and picture operations
Caveat Review release notes for 5.0.9 to check for any breaking changes or configuration adjustments required; standard upgrade precautions apply

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41658 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41658 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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