CVE-2025-59016
BaseFortify
Publication date: 2025-09-09
Last updated on: 2025-09-10
Assigner: TYPO3
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| typo3 | typo3 | From 9.0.0 (inc) to 9.5.55 (exc) |
| typo3 | typo3 | From 10.0.0 (inc) to 10.4.54 (inc) |
| typo3 | typo3 | From 11.0.0 (inc) to 11.5.48 (inc) |
| typo3 | typo3 | From 12.0.0 (inc) to 12.4.37 (inc) |
| typo3 | typo3 | From 13.0.0 (inc) to 13.4.18 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-209 | The product generates an error message that includes sensitive information about its environment, users, or associated data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an information disclosure issue in the TYPO3 CMS File Abstraction Layer. When certain low-level file-system operations fail, error messages reveal the full file paths of files on the server. This exposure happens only to backend users with valid accounts. The problem affects TYPO3 versions 9.0.0 through 13.4.17 and is classified as CWE-209, meaning sensitive information is leaked through error messages. [1]
How can this vulnerability impact me? :
The vulnerability can allow an attacker with backend user access to see full file paths on the server, which could aid in further attacks by revealing the server's directory structure. Although the impact on confidentiality is considered low, this information disclosure can help attackers understand the environment better and potentially exploit other vulnerabilities. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by verifying if your TYPO3 CMS installation is running any of the affected versions (9.0.0-9.5.54, 10.0.0-10.4.53, 11.0.0-11.5.47, 12.0.0-12.4.36, or 13.0.0-13.4.17). Since exploitation requires a valid backend user account and involves error messages disclosing full file paths during failed low-level file operations, you can monitor backend logs for error messages revealing file paths. There are no specific commands provided in the resources to detect the vulnerability directly on the network or system. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating your TYPO3 CMS installation to the fixed versions: 9.5.55 ELTS, 10.4.54 ELTS, 11.5.48 ELTS, 12.4.37 LTS, or 13.4.18 LTS. Additionally, follow the TYPO3 Security Guide recommendations to reduce risk. Restrict backend user access to trusted personnel only, as exploitation requires a valid backend user account. [1]