Admidio has CSRF and Form Validation Bypass in Inventory Item Save via imported Parameter

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-34383: 0.14% estimated exploitation activity in the next 30 days; percentile 3.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The inventory module's itemsave endpoint accepts a user-controllable POST parameter imported that, when set to true, completely bypasses both CSRF token validation and server-side form validation. An authenticated user can craft a direct POST request to save arbitrary inventory item data without CSRF protection and without the field value checks that the FormPresenter validation normally enforces. Details In modules/inventory.php, the imported parameter is read from POST input: File: modules/inventory.php:50 This is then passed to ItemService: File: modules/inventory.php:251-256 Inside ItemService::save(), the postImported flag completely skips CSRF and form validation: File: src/Inventory/Service/ItemService.php:99-109 When imported=1 is sent, the code: 1. Skips $gCurrentSession-getFormObject() — which validates the CSRF token 2. Skips $itemFieldsEditForm-validate() — which sanitizes and validates field values 3. Uses raw $POST values directly to save to the database This…

Published by the source

31 Mar 2026, 23:11 UTC

Last modified by the source

31 Mar 2026, 23:11 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4rwm-c5mj-wh7x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34383

Advisory: Admidio has CSRF and Form Validation Bypass in Inventory Item Save via `imported` Parameter
IDs: CVE-2026-34383, GHSA-4rwm-c5mj-wh7x
Record: https://patchnext.com/advisories/cve-2026-34383 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: admidio/admidio 5.0.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist admidio/admidio: affected <= 5.0.7; fixed in 5.0.8

## Suggested inspection (read-only)
- Packagist admidio/admidio: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on admidio/admidio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4rwm-c5mj-wh7x (GitHub-reviewed advisory GHSA-4rwm-c5mj-wh7x lists affected ranges: Packagist admidio/admidio >=0 <=5.0.7)

Commands are suggestions: review each one before running it.