CVE-2023-50462 — content-consent
MEDIUMCVE-2023-50462 is a medium-severity (CVSS 5.3) CWE-863 vulnerability in t3s/content-consent. A fix is available for t3s/content-consent — see the affected versions and patch details below.
Insecure Direct Object Reference in extension "Content Consent" (content_consent)
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-50462.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
t3s/content-consent🐘t3s/content-consentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | t3s/content-consent | ≥ 2.0.0&&< 2.0.2 | 2.0.2composer require t3s/content-consent:^2.0.2 |
| 🐘Packagist | t3s/content-consent | all versions | 1.0.3composer require t3s/content-consent:^1.0.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for t3s/content-consent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update t3s/content-consent to 2.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-50462 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2023-50462 in your dependencies?
Find it across Packagist, including transitive dependencies.