Extension Syssy Typo3 Monitoring Security Checks
Monthly
Insufficient JWT expiration validation in the TYPO3 'Syssy - TYPO3 Monitoring & Security Checks' extension allows an attacker already in possession of a valid SYSSY project API key to authenticate using an expired token, bypassing the intended session time boundary (CWE-613). The limited confidentiality and integrity impact (VC:L/VI:L per the CVSS 4.0 vector) reflects access to monitoring and security check data rather than full system compromise. No active exploitation has been confirmed (not listed in CISA KEV), and no public exploit code has been identified at time of analysis.
Cleartext transmission of TYPO3 system information occurs in the Syssy - TYPO3 Monitoring & Security Checks extension when OpenSSL is absent on the hosting server, exposing potentially sensitive configuration and system data to network interception (CWE-319). All tracked versions of the extension are affected per CPE data, though exploitation is constrained by the dual requirement of OpenSSL being unavailable and the attacker already possessing the SYSSY project's API key. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog; the CVSS 4.0 score of 5.3 reflects the medium-severity, partially-authenticated nature of the flaw.
Insufficient JWT expiration validation in the TYPO3 'Syssy - TYPO3 Monitoring & Security Checks' extension allows an attacker already in possession of a valid SYSSY project API key to authenticate using an expired token, bypassing the intended session time boundary (CWE-613). The limited confidentiality and integrity impact (VC:L/VI:L per the CVSS 4.0 vector) reflects access to monitoring and security check data rather than full system compromise. No active exploitation has been confirmed (not listed in CISA KEV), and no public exploit code has been identified at time of analysis.
Cleartext transmission of TYPO3 system information occurs in the Syssy - TYPO3 Monitoring & Security Checks extension when OpenSSL is absent on the hosting server, exposing potentially sensitive configuration and system data to network interception (CWE-319). All tracked versions of the extension are affected per CPE data, though exploitation is constrained by the dual requirement of OpenSSL being unavailable and the attacker already possessing the SYSSY project's API key. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog; the CVSS 4.0 score of 5.3 reflects the medium-severity, partially-authenticated nature of the flaw.