# CVE-2026-38474: Missing authorization in n/a

> Authenticated users can modify IP lock entries for other accounts, bypassing access controls in GazellePW.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-v7wf-gpp7-vjcw

## What is CVE-2026-38474?

CVE-2026-38474 is a medium-severity missing authorization vulnerability in n/a, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GazellePW (GazellePosterWall) commit 86c4bedf727691b5a97af42a4864869d18446449 suffers from a Broken access control vulnerability in the IP lock manager, which allows remote authenticated users to add, modify, or delete IP lock entries for arbitrary accounts via tools.php?action=iplock.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-38474?


## How do I fix CVE-2026-38474?

No fix has been published for CVE-2026-38474 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-38474 being exploited?

There is no known exploitation of CVE-2026-38474 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-38474 and fix it if it is affected.

What it is: CVE-2026-38474 is a medium-severity missing authorization vulnerability in n/a, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-38474 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-38474/ (Markdown: https://insights.sbomify.com/CVE-2026-38474/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-38474
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-38474
- OSV: https://osv.dev/vulnerability/CVE-2026-38474

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-38474/
Summaries are generated and may contain mistakes; the official description above is the record.