High

TYPO3 Security Misconfiguration for Backend User Accounts

  • Disclosed: 07.06.2024
  • Updated: 11.10.2026 10:22

When using the TYPO3 backend in order to create new backend user accounts, database records containing insecure or empty credentials might be persisted. When the type of user account is changed - which might be entity type or the admin flag for backend users - the backend form is reloaded in order to reflect changed configuration possibilities. However, this leads to persisting the current state as well, which can result into some of the following:

  • account contains empty login credentials (username and/or password)
  • account is incomplete and contains weak credentials (username and/or password)

Albeit the functionality provided by the TYPO3 core cannot be used either with empty usernames or empty passwords, it still can be a severe vulnerability to custom authentication service implementations.

This weakness cannot be directly exploited and requires interaction on purpose by some backend user having according privileges.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package typo3/cms >= 8.0.0, < 8.7.23, >= 9.0.0, < 9.5.4 8.7.23, 9.5.4

References

CVSS score 7.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Weakness (CWE)
CWE-287
Platform
Composer
Package
typo3/cms
Disclosed
07.06.2024
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-c5mj-39cf-3pp5 - CC BY 4.0

Vulnerability history: typo3/cms

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (188) in the archive
Total entries
188
First → latest
09.2018 06.2024
Without a fix
3
Exploited in attacks
0

Severity breakdown

  • Critical 6
  • High 41
  • Medium 128
  • Low 13

Disclosures per year

  1. 2018: 2
  2. 2019: 0
  3. 2020: 13
  4. 2021: 15
  5. 2022: 85
  6. 2023: 1
  7. 2024: 72
  8. 2025: 0
  9. 2026: 0
Severity:
  1. High · 8.1 ghsa-f777-f784-36gm >= 7.0.0, < 7.6.32, >= 8.0.0, < 8.7.21, >= 9.0.0, < 9.5.2 7.6.32, 8.7.21, 9.5.2
  2. High · 8.8 ghsa-8h4m-r4wm-xj7r >= 8.0.0, < 8.7.23, >= 9.0.0, < 9.5.4 8.7.23, 9.5.4
  3. High · 7.5 ghsa-g585-crjf-vhwq >= 7.0.0, < 7.6.32, >= 8.0.0, < 8.7.21 7.6.32, 8.7.21
  4. TYPO3 Security Misconfiguration for Backend User Accounts this entry
    High · 7.3 ghsa-c5mj-39cf-3pp5 >= 8.0.0, < 8.7.23, >= 9.0.0, < 9.5.4 8.7.23, 9.5.4
  5. High · 8.1 ghsa-hh95-5xm5-v8v7 >= 8.0.0, < 8.7.30, >= 9.0.0, < 9.5.12 8.7.30, 9.5.12
  6. High ghsa-ppgf-8745-8pgx >= 7.0.0, < 7.6.30, >= 8.0.0, < 8.7.17, >= 9.0.0, < 9.3.2 7.6.30, 8.7.17, 9.3.2
  7. High · 8.8 ghsa-7qwg-fcpw-xg5g >= 8.5.0, < 8.7.17, >= 9.0.0, < 9.3.2 8.7.17, 9.3.2
  8. High ghsa-g4pf-3jvq-2gcw >= 6.2.0, < 6.2.30, >= 7.6.0, < 7.6.15, >= 8.0.0, < 8.5.1 6.2.30, 7.6.15, 8.5.1
  9. Critical · 9.9 ghsa-67wg-6j7r-mqh8 >= 7.6.0, < 7.6.22, >= 8.0.0, < 8.7.5 7.6.22, 8.7.5
  10. High ghsa-8h28-f46f-m87h >= 8.5.0, < 8.7.17, >= 9.0.0, < 9.3.2 8.7.17, 9.3.2
  11. Critical · 9.0 ghsa-gwfx-p7mr-f92v >= 6.2.0, < 6.2.25, >= 7.6.0, < 7.6.8, >= 8.0.0, < 8.1.1 6.2.25, 7.6.8, 8.1.1
  12. High ghsa-qffc-gwpp-m2xr >= 6.2.0, < 6.2.19, >= 7.6.0, < 7.6.4 6.2.19, 7.6.4
  13. High ghsa-9895-53fc-98v2 >= 6.2.0, < 6.2.18 6.2.18
  14. High · 7.1 ghsa-r9vc-jfmh-6j48 >= 6.2.0, < 6.2.14, >= 7.0.0, < 7.3.1 6.2.14, 7.3.1
  15. High · 8.8 ghsa-4r76-xr68-w7m7 >= 6.2.0, < 6.2.14, >= 7.0.0, < 7.3.1 6.2.14, 7.3.1
  16. High ghsa-p84g-j2gh-83g3 >= 6.2.0, < 6.2.9, >= 7.0.0, < 7.0.2 6.2.9, 7.0.2
  17. High · 8.1 ghsa-45xg-4w5x-j429 >= 6.2.0, < 6.2.6, >= 6.1.0, < 6.1.12, >= 4.7.0, < 4.7.20, >= 4.5.0, < 4.5.37 6.2.6, 6.1.12, 4.7.20, 4.5.37
  18. High · 8.8 CVE-2023-24814 >= 10.0.0, < 10.4.35, >= 11.0.0, < 11.5.23, >= 12.0.0, < 12.2.0 10.4.35, 11.5.23, 12.2.0
  19. Critical · 9.8 CVE-2022-47406 < 2.0.5, >= 3.0.0, < 3.0.3 2.0.5, 3.0.3
  20. High · 7.5 CVE-2022-23503 >= 10.0.0, < 10.4.33, >= 11.0.0, < 11.5.20, >= 12.0.0, < 12.1.1 10.4.33, 11.5.20, 12.1.1
Show more (20) Showing 20 of 47

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.