# CVE-2026-77132: TYPO3 CMS - Information Disclosure via Backend Localization Wizard

> Authenticated low-privileged backend users can access unauthorized record information due to missing authorization checks in the localization wizard.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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:** 8 Sep 2026
- **Updated:** 8 Sep 2026

## What is CVE-2026-77132?

CVE-2026-77132 is a medium-severity missing authorization vulnerability in TYPO3 CMS, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

It has been discovered that several AJAX routes used for the backend localization wizard failed to perform authorization checks. This allowed authenticated, low-privileged backend users to access information about records and content elements that fall outside of their permitted range. Exploiting this vulnerability requires a low-privileged backend user account. This issue affects TYPO3 CMS versions 10.0.0-10.4.59, 11.0.0-11.5.53, 12.0.0-12.4.48, 13.0.0-13.4.34 and 14.0.0-14.3.6.

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-77132 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77132 is a medium-severity missing authorization vulnerability in TYPO3 CMS, published on 8 Sep 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-77132 in the wild and no public exploit code.

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

## Sources

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

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