-
Stephan Großberndt authored
Further improvements, most of them as proposed by Michael Schams Releases: main Resolves: #100755 Related: #100747 Related: #100740 Change-Id: I4111a8e1025eb7c2e5e5c3273e320505c153e4ec Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/78875 Reviewed-by:
Michael Schams <typo3.mschams@2023.schams.net> Tested-by:
Torben Hansen <derhansen@gmail.com> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
core-ci <typo3@b13.com> Tested-by:
Thomas Hohn <tho@gyldendal.dk> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
f98773ec
Security Policy
Supported Versions
The following matrix shows the TYPO3 versions currently maintained by the TYPO3 community. Sprint releases (versions before 12.4.0 and 11.5.0, in their corresponding branches) have reached their end of support and don't receive any further bug fixes or security patches.
| Version | Supported |
|---|---|
| 12.4.x | |
| 12.3.x | |
| 12.2.x | |
| 12.1.x | |
| 12.0.x | |
| 11.5.x | |
| < 11.5.0 |
Reporting a Vulnerability
Please report vulnerabilities to security@typo3.org. Your report should include the following details:
- The affected project (either the TYPO3 Core or a TYPO3 extension).
- The exact version or version range that you analysed.
- A step-by-step explanation of how to exploit the potential vulnerability.
You can use the following GPG/PGP key ID to optionally encrypt your messages to security@typo3.org:
- Key ID:
C05FBE60 - Fingerprint:
B41C C3EF 373E 0F5C 7018 7FE9 3BEF BD27 C05F BE60
You can download the public key from the following sources:
Coordinated Disclosure
⚠ We urge security researchers not to publish vulnerabilities in issue trackers or discuss them publicly (e.g. on Slack or Twitter).
The TYPO3 Security Team coordinates the process with the TYPO3 core developers, extension maintainers and other affected parties. Once a security fix is available, we prepare a new release and publish the fixed version. At the same time, we communicate the vulnerability and the fix to the public by using various communication channels such as:
- TYPO3 Security Advisories
- TYPO3 Security Team on Twitter
- #announce channel on Slack
- TYPO3 Announce Mailing List
The TYPO3 Security Team takes care of requesting CVE IDs (Common Vulnerabilities and Exposures identifiers).
TYPO3 Release Dates ("Patchday")
We aim to publish TYPO3 maintenance releases on Tuesdays as a general rule. However, exceptions apply (e.g. public holidays). Release dates of maintenance releases are scheduled in advance. These releases can contain security fixes.