Quick answers
- Is CVE-2026-85395 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85395 being exploited in the wild.
- How severe is CVE-2026-85395?
- High severity, with a CVSS score of 7.1, published 3 September 2026.
- Which products and versions are affected?
- UnoPim before 2.1.3.
- Is there a fix for CVE-2026-85395?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-85395 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-85395?
- Check whether you run UnoPim 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.
Technical details
UnoPim uses a custom ACL middleware (Bouncer) to enforce permissions on routes, but the integration management routes (store, update, and key-generation) are missing from the ACL configuration map. When a request arrives for an unregistered route, the checkIfAuthorized() function in Bouncer.php returns without performing any permission validation. An authenticated admin attacker can exploit this by calling the unprotected POST /admin/integrations/api-keys/create and /admin/integrations/api-keys/generate endpoints to create an OAuth integration tied to a superadmin account, mint client credentials, and escalate to full API access. No secondary authorization checks exist in the ApiKeysController methods. The vulnerability requires only admin-level authentication and network access; no user interaction is needed.
Affected products
- UnoPim UnoPim before 2.1.3
Timeline
- 2026-09-03: disclosed
- other: Confirmed vulnerable in commit 3e894245 (v2.1.2)