Quick answers
- Is CVE-2026-38474 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-38474 being exploited in the wild.
- How severe is CVE-2026-38474?
- Medium severity, with a CVSS score of 5.4, published 25 August 2026.
- Which products and versions are affected?
- Mosasauroidea GazellePW commit 86c4bedf727691b5a97af42a4864869d18446449 and likely earlier.
- Is there a fix for CVE-2026-38474?
- 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-38474 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-38474?
- 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
GazellePW's IP lock manager in tools.php (action=iplock) implements the IPLock class for managing per-user IP whitelists. The vulnerability is a broken access control flaw where the add(), edit(), and delete() methods lack proper authorization checks—they only validate UserID via intval() but do not verify that the authenticated user performing the operation has permission to modify IP locks for the target account. An authenticated attacker can directly call these functions via the tools.php interface to add, modify, or delete IP lock entries for arbitrary user accounts. No special privileges, user interaction, or network bypasses are required beyond authentication. This allows an attacker to lock out legitimate users or grant themselves access to restricted accounts.
Affected products
- Mosasauroidea GazellePW commit 86c4bedf727691b5a97af42a4864869d18446449 and likely earlier
Timeline
- 2026-08-25: disclosed
- other: CVE-2026-38474 assigned