Vendor
Security Bypass Vulnerability in TYPO3 Femanager Extension
1 TTP 1 CVEA vulnerability in the TYPO3 Femanager extension (CVE-2024-42023) allows remote, unauthenticated attackers to bypass security mechanisms, potentially leading to unauthorized access within the CMS environment.
Multiple Vulnerabilities in TYPO3 Extensions
2 TTPsMultiple security flaws in various TYPO3 extensions enable remote authenticated or anonymous attackers to bypass security controls, perform information disclosure, and execute arbitrary code.
Broken Access Control in TYPO3 CMS Backend and Install Tool
2 TTPsTYPO3 CMS versions 13.0.0 through 13.4.33 and 14.0.0 through 14.3.5 contain a broken access control vulnerability (CVE-2026-19418) that allows attackers to perform unauthorized actions by abusing ineffective referrer enforcement.
Unauthenticated Access Control Vulnerability in TYPO3 Club Directory
1 TTP 1 CVEAn unauthenticated broken access control vulnerability in the TYPO3 Club Directory extension allows remote attackers to overwrite or publish club records by supplying a known record UID to frontend actions.
TYPO3 Core Security Restriction Bypass Vulnerability
1 TTP 1 CVEA vulnerability in TYPO3 Core identified as CVE-2024-51978 allows a remote, authenticated attacker to bypass security restrictions within the framework.
Multiple Vulnerabilities in Typo3 Leading to RCE, Privilege Escalation, and Data Compromise
3 rules 6 TTPs 5 CVEs 20 IOCsMultiple vulnerabilities discovered in Typo3 allow an attacker to achieve remote arbitrary code execution, privilege escalation, data confidentiality compromise, data integrity compromise, security policy bypass, remote indirect code injection (XSS), and SQL injection (SQLi).
Multiple Vulnerabilities in TYPO3 Extensions
2 rules 1 TTPMultiple vulnerabilities in TYPO3 extensions allow an attacker to execute arbitrary program code, conduct SQL injection attacks, disclose information, and circumvent security measures.
TYPO3 CMS 14.2.0 Stores Passwords in Cleartext
1 rule 1 TTPTYPO3 CMS version 14.2.0 stores passwords in cleartext in the `uc` and `user_settings` fields of the `be_users` database table when users change their credentials in the backend user settings module.