Quick answers
- Is CVE-2026-34383 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34383 being exploited in the wild.
- How severe is CVE-2026-34383?
- Medium severity, with a CVSS score of 4.3, published 31 March 2026.
- Which products and versions are affected?
- Admidio < 5.0.8; admidio/admidio (Packagist) ECOSYSTEM:introduced=0,fixed=5.0.8.
- Is there a fix for CVE-2026-34383?
- Yes. admidio/admidio (Packagist): upgrade to 5.0.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34383 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-34383?
- Check whether you run Admidio or admidio/admidio (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- admidio/admidio (Packagist): upgrade to 5.0.8 or later
composer require admidio/admidio:^5.0.8
Technical details
A vulnerability exists in the 'item_save' endpoint of Admidio's inventory module due to improper handling of the 'imported' POST parameter. When this parameter is set to true, the application's ItemService::save() method skips both CSRF token verification and server-side form validation (FormPresenter). An authenticated attacker can exploit this by sending a direct POST request with raw, unsanitized data. This bypass allows for Cross-Site Request Forgery (CSRF) attacks and the injection of arbitrary data into the database, which may result in stored Cross-Site Scripting (XSS) if the data is later rendered without proper encoding. The issue is fixed in version 5.0.8 by ensuring validation occurs regardless of the import flag.
Affected products
- Admidio Admidio < 5.0.8
Identifiers
- CVE-2026-34383
- GHSA-4rwm-c5mj-wh7x
Timeline
- 2026-03-27: advisory: GitHub Security Advisory published
- 2026-03-31: disclosed: CVE-2026-34383 published
- 2026-03-31: patched: Fixed in version 5.0.8