CVE-2023-50462 Overview
CVE-2023-50462 affects the content_consent (Content Consent) extension for TYPO3 through version 2.0.1. The extension fails to verify whether a specified content element identifier is permitted by the plugin. Unauthenticated attackers can request arbitrary content element IDs and cause the plugin to render them. This produces an Insecure Direct Object Reference (IDOR) condition that can expose internal content elements not intended for public viewing. The weakness is classified as [CWE-863] Incorrect Authorization.
Critical Impact
An unauthenticated remote attacker can enumerate content element identifiers and disclose internal TYPO3 content through the vulnerable Content Consent plugin.
Affected Products
- TYPO3 content_consent extension versions through 2.0.1
- TYPO3 installations using the Content Consent plugin
- Any public-facing TYPO3 site that renders consent-gated content elements
Discovery Timeline
- 2026-09-14 - CVE-2023-50462 published to the National Vulnerability Database
- 2026-09-14 - Last updated in NVD database
Technical Details for CVE-2023-50462
Vulnerability Analysis
The Content Consent extension for TYPO3 renders content elements based on an identifier supplied in the request. The plugin does not validate whether the supplied identifier belongs to the set of content elements configured as consent-managed. An unauthenticated user can substitute any content element ID and receive the rendered output. This behavior maps to [CWE-863] Incorrect Authorization because the authorization decision is missing from the render path. The impact is limited to confidentiality; integrity and availability are not affected.
Root Cause
The root cause is missing authorization on the content element identifier parameter. The plugin trusts the request parameter without cross-referencing an allow-list of permitted element IDs. Any element the TYPO3 backend can render becomes reachable through the plugin endpoint.
Attack Vector
Exploitation occurs over the network without authentication or user interaction. An attacker crafts a request to the Content Consent plugin endpoint and substitutes the content element identifier with a value pointing to internal or restricted content. The server processes the request and returns the requested element. No exploit code is required beyond modifying a URL parameter or form field. See the TYPO3 Security Advisory TYPO3-EXT-SA-2023-009 for the coordinated disclosure details.
No public proof-of-concept has been released, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. The EPSS score is 0.267%.
Detection Methods for CVE-2023-50462
Indicators of Compromise
- Unexpected HTTP requests to the Content Consent plugin endpoint containing content element identifiers that vary across a short time window
- Web server access logs showing enumeration patterns against the plugin URL, especially sequential or scripted parameter values
- Rendered internal content elements appearing in outbound HTTP responses to unauthenticated clients
Detection Strategies
- Inventory TYPO3 installations and identify sites running the content_consent extension at version 2.0.1 or earlier
- Review web application firewall logs for parameter tampering targeting the Content Consent plugin
- Correlate anonymous session activity with requests that return content element IDs outside the configured consent scope
Monitoring Recommendations
- Enable verbose logging on the TYPO3 frontend for plugin-rendered requests
- Alert on high-rate requests from single source IPs against the Content Consent endpoint
- Baseline the set of content element IDs legitimately rendered through the plugin and flag deviations
How to Mitigate CVE-2023-50462
Immediate Actions Required
- Upgrade the content_consent extension to a fixed release above 2.0.1 as directed in the TYPO3 advisory
- Audit consent-managed content elements and confirm none contain sensitive or internal-only data
- Restrict access to the TYPO3 frontend plugin endpoint from untrusted networks where operationally feasible
Patch Information
The TYPO3 project has published fixed versions of the Content Consent extension. Refer to the TYPO3 Security Advisory TYPO3-EXT-SA-2023-009 for the specific fixed version and upgrade instructions. Apply the patched release through the TYPO3 Extension Manager or Composer.
Workarounds
- Disable the content_consent extension until a patched version can be deployed
- Deploy a web application firewall rule that restricts the accepted content element identifier parameter to a known allow-list
- Remove or relocate sensitive content elements so they are not addressable by the plugin endpoint
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
