Quick answers
- Is CVE-2026-38470 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-38470 being exploited in the wild.
- How severe is CVE-2026-38470?
- Medium severity, with a CVSS score of 4.3, published 25 August 2026.
- Which products and versions are affected?
- Mosasauroidea GazellePW commit 86c4bedf727691b5a97af42a4864869d18446449 and prior.
- Is there a fix for CVE-2026-38470?
- 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-38470 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-38470?
- Check whether you run Mosasauroidea GazellePW 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
A broken access control vulnerability exists in the GazellePW API user endpoint (app/API/User.php) where the enableUser() and disableUser() methods lack proper authorization verification. An authenticated user with a valid API token can invoke the req=enable or req=disable action to manipulate the Enabled status of arbitrary user accounts by supplying a target user_id or username parameter. The vulnerable code does not verify that the requestor has the necessary privileges before executing account enable/disable operations. This allows any authenticated API user to perform administrative actions, effectively escalating their privileges. The issue affects commit 86c4bedf727691b5a97af42a4864869d18446449 and likely other versions before patching.
Affected products
- Mosasauroidea GazellePW commit 86c4bedf727691b5a97af42a4864869d18446449 and prior
Timeline
- 2026-08-25: disclosed