Description
The extension fails to properly validate the expiration of a client-supplied JWT token, allowing an attacker in control of a valid API key to authenticate with an expired token. Exploitation requires the attacker to already be in control of the SYSSY project's API key.
Published: 2026-08-25
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Authentication
Action: Assess Impact
AI Analysis

Impact

The SYSSY extension fails to verify the expiration field on client‑supplied JSON Web Tokens, which enables an attacker who already controls a valid API key to use an expired token for authentication. This bypasses the intended lifetime restriction and can allow continued access to the protected API beyond the intended timeframe, potentially enabling unauthorized actions within the TYPO3 environment.

Affected Systems

TYPO3 installations that have the SYSSY – TYPO3 Monitoring & Security Checks extension installed are affected. Specific version information is not provided in the advisory, so all deployed versions of the extension are potentially vulnerable.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity, and the EPSS score is not available. This vulnerability is not listed in the CISA KEV catalog. Exploitation requires possession of a valid API key for the SYSSY project; after that, the attacker can authenticate with an expired token through the API endpoint. No additional privileges or local compromise are required to leverage this flaw.

Generated by OpenCVE AI on August 25, 2026 at 10:51 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Rotate or regenerate any SYSSY API keys to eliminate reliance on potentially compromised credentials.
  • Disable or remove the SYSSY extension if it is not essential, or request a vendor patch that properly validates token expiration.
  • Configure server‑side checks to enforce JWT expiration and reject any token whose expiration timestamp has passed, ensuring that authentication strictly respects the intended validity period.

Generated by OpenCVE AI on August 25, 2026 at 10:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 28 Aug 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Typo3
Typo3 extension "syssy - Typo3 Monitoring & Security Checks"
Vendors & Products Typo3
Typo3 extension "syssy - Typo3 Monitoring & Security Checks"

Tue, 25 Aug 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 25 Aug 2026 09:15:00 +0000

Type Values Removed Values Added
Description The extension fails to properly validate the expiration of a client-supplied JWT token, allowing an attacker in control of a valid API key to authenticate with an expired token. Exploitation requires the attacker to already be in control of the SYSSY project's API key.
Title Insufficient Session Expiration in extension "SYSSY - TYPO3 Monitoring & Security Checks" (syssy)
Weaknesses CWE-613
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Typo3 Extension "syssy - Typo3 Monitoring & Security Checks"
cve-icon MITRE

Status: PUBLISHED

Assigner: TYPO3

Published:

Updated: 2026-08-25T14:51:54.258Z

Reserved: 2026-08-20T13:10:12.062Z

Link: CVE-2026-77130

cve-icon Vulnrichment

Updated: 2026-08-25T14:46:16.424Z

cve-icon NVD

Status : Deferred

Published: 2026-08-25T09:17:33.360

Modified: 2026-08-26T17:13:53.420

Link: CVE-2026-77130

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-28T20:37:38Z

Weaknesses
  • CWE-613

    Insufficient Session Expiration