CVE-2026-112065 TYPO3 CVE debrief

Who should care

Defenders responsible for securing backend user access and consent data should assess the vulnerability's impact on their systems. This includes operators, security teams, and vulnerability management teams who need to verify the vulnerability's impact on their systems and assess the need for additional access controls to prevent unauthorized access to consent data.

Why it matters

CVE-2026-112065 is a medium-severity vulnerability that could allow authenticated backend users to retrieve consent data of any site in the installation. Defenders should prioritize verifying the vulnerability's impact on their systems and assess the need for additional access controls.

• Potential unauthorized access to consent data
• Need for additional access controls to prevent data exposure
• Verification of vulnerability impact on specific systems and versions

Technical summary

The routes that provide consent history and statistics data did not check whether the backend user had access to the module or to the requested page. Any authenticated backend user, regardless of permissions, could therefore retrieve consent data of any site in the installation. This vulnerability could allow authenticated backend users to retrieve consent data of any site in the installation, potentially leading to unauthorized access to sensitive information. The affected product and versions are not specified in the CVE record or NVD entry.

Defensive priority

Defenders should prioritize verifying the vulnerability's impact on their systems, especially if they use the affected product, and assess the need for additional access controls.

Recommended defensive actions

• Verify the vulnerability's impact on your systems, especially if you use the affected product.
• Assess the need for additional access controls to prevent unauthorized access to consent data.
• Monitor for any updates or patches from the vendor.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. Further investigation is needed to determine the affected product and versions. The routes that provide consent history and statistics data did not check whether the backend user had access to the module or to the requested page. Any authenticated backend user, regardless of permissions, could therefore retrieve consent data of any site in the installation. The CVE record was published on 2026-10-20T10:17:03.630Z and has not been modified since then.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.