<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cve-2026-6553 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-6553/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 30 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-6553/feed.xml" rel="self" type="application/rss+xml"/><item><title>TYPO3 CMS 14.2.0 Stores Passwords in Cleartext</title><link>https://feed.craftedsignal.io/briefs/2024-01-typo3-cleartext-passwords/</link><pubDate>Tue, 30 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-typo3-cleartext-passwords/</guid><description>TYPO3 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.</description><content:encoded><![CDATA[<p>TYPO3 CMS version 14.2.0 contains a vulnerability where user passwords are stored in cleartext within the <code>uc</code> and <code>user_settings</code> fields of the <code>be_users</code> database table. This issue arises due to the <code>SetupModuleController</code> incorrectly conflating entity data with user-interface settings during persistence. The vulnerability is triggered when backend users modify their credentials through the backend user settings module while using the affected TYPO3 version. This flaw, reported by Martin Clewing and addressed by the TYPO3 core team, poses a significant risk as it exposes user credentials to unauthorized access and potential compromise. Defenders should prioritize upgrading to TYPO3 version 14.3.0 LTS and executing the User Settings Scrubbing wizard.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains unauthorized access to the TYPO3 backend, potentially through brute-force attacks or stolen credentials.</li>
<li>The attacker navigates to the backend user settings module.</li>
<li>A legitimate user or the attacker changes their password within the module while the TYPO3 instance is running version 14.2.0.</li>
<li>The <code>SetupModuleController</code> processes the password change request.</li>
<li>Instead of properly hashing the password, the <code>SetupModuleController</code> stores it in cleartext in the <code>uc</code> and <code>user_settings</code> fields of the <code>be_users</code> database table.</li>
<li>An attacker with database access can now retrieve the cleartext passwords from these fields.</li>
<li>The attacker uses the compromised credentials to impersonate the user and gain access to sensitive data or perform unauthorized actions.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows attackers with database access to retrieve cleartext passwords, potentially leading to complete compromise of backend user accounts. While the vulnerability is limited to TYPO3 CMS version 14.2.0, the impact on affected instances is significant, as administrative accounts could be hijacked, allowing attackers to modify website content, install malicious extensions, or exfiltrate sensitive data. This could result in data breaches, financial loss, and reputational damage.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade to TYPO3 version 14.3.0 LTS to address the underlying vulnerability (reference: Solution section).</li>
<li>Execute the User Settings Scrubbing wizard in the TYPO3 Install Tool to sanitize existing cleartext passwords in the <code>uc</code> and <code>user_settings</code> fields (reference: Solution section).</li>
<li>Require affected backend user accounts to reset their passwords immediately (reference: Solution section).</li>
<li>Monitor database access logs for suspicious activity, especially access to the <code>be_users</code> table (reference: Attack Chain).</li>
<li>Deploy the Sigma rule provided below to detect potential unauthorized access attempts following password changes.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>typo3</category><category>cleartext-password</category><category>credential-access</category><category>cve-2026-6553</category></item></channel></rss>