# CVE-2026-47366: Privilege escalation in phpBB

> Authenticated administrators can escalate privileges beyond their authorized level via the Administration Control Panel, requiring a patch for phpBB.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-f8mc-8mhv-jcrc

## What is CVE-2026-47366?

CVE-2026-47366 is a high-severity vulnerability in phpBB, published on 12 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper verification of access permissions when modifying permissions through the Administration Control Panel (ACP) allowed an authenticated administrator to grant permissions beyond the level authorized for their account, resulting in privilege escalation within the administrative interface.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-47366 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47366 is a high-severity vulnerability in phpBB, published on 12 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47366 in the wild and no public exploit code.

Affected product: phpBB. 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-47366/ (Markdown: https://insights.sbomify.com/CVE-2026-47366/index.md)
```

## Sources

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

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