# CVE-2023-50462: Insecure Direct Object Reference in extension "Content Consent" (content_consent)

> Unauthenticated attackers can view internal content elements due to missing authorization checks in the Content Consent extension.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-j8cw-ppmv-wj85

## What is CVE-2023-50462?

CVE-2023-50462 is a medium-severity missing authorization vulnerability in TYPO3 content_consent, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the content_consent (aka Content Consent) extension through 2.0.1 for TYPO3. It fails to verify whether a specified content element identifier is permitted by the plugin. This enables an unauthenticated user to display various content elements, leading to an insecure direct object reference (IDOR) issue with the potential to expose internal content elements.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-50462?

4 open source packages ship an affected version, including t3s/content-consent.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `t3s/content-consent` | Packagist | All versions | 1.0.3 |
| `t3s/content-consent` | Packagist | All versions | 1.0.3 |
| `t3s/content-consent` | Packagist | From 2.0.0 | 2.0.2 |
| `t3s/content-consent` | Packagist | From 2.0.0 | 2.0.2 |

## How do I fix CVE-2023-50462?

Upgrade t3s/content-consent to a fixed version for your release line: 1.0.3 or 2.0.2.

## Is CVE-2023-50462 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50462 and fix it if it is affected.

What it is: CVE-2023-50462 is a medium-severity missing authorization vulnerability in TYPO3 content_consent, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-50462 in the wild and no public exploit code.

Affected packages and fixed versions:
- t3s/content-consent (Packagist): affected all versions; fixed in 1.0.3
- t3s/content-consent (Packagist): affected all versions; fixed in 1.0.3
- t3s/content-consent (Packagist): affected from 2.0.0; fixed in 2.0.2
- t3s/content-consent (Packagist): affected from 2.0.0; fixed in 2.0.2

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-2023-50462/ (Markdown: https://insights.sbomify.com/CVE-2023-50462/index.md)
```

## Sources

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

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