⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.3

How to Fix CVE-2026-6553: Cleartext storage of sensitive information in TYPO3 CMS

By Sai Kiran Pandrala. Last verified: 2026-05-25.

⚡ At a glance
Severity7.3 (High)
Actively exploited?No public listing in CISA KEV
AffectedTYPO3 14.2.0 to <14.3.0
Fixed inTYPO3 CMS 14.3.0
Type (CWE)CWE-312: Cleartext storage of sensitive information

What is CVE-2026-6553?

Changing backend users' passwords via the user settings module results in storing the cleartext password in the uc and user_settings fields of the be_users database table. This issue affects TYPO3 CMS version 14.2.0.

Am I affected?

Run the version check that matches your platform:


# Windows
winget list | findstr /I "typo3"
Get-WmiObject Win32_Product | Where-Object { $_.Name -like "*TYPO3 CMS*" } | Select-Object Name, Version

Compare what you see against the Affected row above (TYPO3 14.2.0 to <14.3.0). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2026-6553

The primary fix is to upgrade TYPO3 CMS to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: TYPO3 CMS 14.3.0.

Windows (PowerShell, run as administrator)


# Check installed version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

# Apply latest Microsoft security updates (Windows Update)
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck
Import-Module PSWindowsUpdate
Get-WindowsUpdate -MicrosoftUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -AutoReboot

# Or via winget for application-level patches
winget upgrade --all --accept-source-agreements --accept-package-agreements

If the affected component is a third-party application, identify the package and run:


winget upgrade --id <vendor.product>

Replace <vendor.product> with the actual winget identifier (run winget search TYPO3 CMS to find it).

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-6553 affecting TYPO3 CMS
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-6553-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detecting installed version of TYPO3 CMS"
    $pkg = winget list --id "TYPO3_CMS" 2>$null
    Write-Host $pkg

    Write-Host "[2/4] Backing up configuration"
    $backup = "C:\Backup\TYPO3_CMS-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\TYPO3_CMS" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Applying upgrade to TYPO3 CMS 14.3.0"
    winget upgrade --id "TYPO3_CMS" --silent --accept-source-agreements --accept-package-agreements
    # Fallback: Windows Update for OS-level fixes
    if ($LASTEXITCODE -ne 0) {
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verifying patched build"
    winget list --id "TYPO3_CMS"
    Write-Host "Fix applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-6553 affecting TYPO3 CMS
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-6553-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
    dpkg -s typo3 2>/dev/null | grep -i version || echo "typo3 not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q typo3 || echo "typo3 not installed via rpm"
fi

echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2026-6553-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/typo3 /etc/typo3.d /etc/typo3.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Applying upgrade (target: TYPO3 CMS 14.3.0)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y typo3
elif command -v dnf >/dev/null; then
    dnf upgrade --security -y typo3
elif command -v yum >/dev/null; then
    yum update -y typo3
elif command -v zypper >/dev/null; then
    zypper --non-interactive patch --category security
fi

echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
    dpkg -s typo3 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
    rpm -q typo3
fi
echo "Done. Restart any running daemons that loaded the old library."

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Windows firewall isolation


# Allow only management subnet to reach the vulnerable service
New-NetFirewallRule -DisplayName "Restrict TYPO3 CMS" `
    -Direction Inbound -Action Block -RemoteAddress Any `
    -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Allow Mgmt TYPO3 CMS" `
    -Direction Inbound -Action Allow -RemoteAddress 10.0.0.0/8 `
    -Protocol TCP -LocalPort 443

Service-level fallback


# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop typo3
sudo systemctl disable typo3

How to verify the fix worked


# Linux
typo3 --version 2>/dev/null || dpkg -s typo3 | grep -i version
rpm -q typo3 2>/dev/null || true


# Windows
winget list | findstr /I "typo3"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above TYPO3 CMS 14.3.0. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-6553 actually being exploited?

According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

7.3 (high). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*