dbcve.org
TYPO3CMS

CVE-2022-23502

MEDIUM · 5.4 CVSS v3.1 Published 2022-12-14
Fix available
A fix is available. Upgrade to 10.4.33 / 11.5.20 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
TYPO3 is an open source PHP based web content management system. In versions prior to 10.4.33, 11.5.20, and 12.1.1, When users reset their password using the corresponding password recovery functionality, existing sessions for that particular user account were not revoked. This applied to both frontend user sessions and backend user sessions. This issue is patched in versions 10.4.33, 11.5.20, 12.1.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

TYPO3 versions prior to 10.4.33, 11.5.20, and 12.1.1 fail to revoke existing user sessions when a password is reset. This affects both frontend and backend sessions, allowing an attacker with a compromised session to retain access even after the legitimate user resets their password.

MitigationUpgrade to TYPO3 versions 10.4.33, 11.5.20, or 12.1.1. Alternatively, manually invalidate all active sessions for affected users via the backend until patching is possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TYPO3CMS
Affected:>= 10.0.0, < 10.4.33>= 11.0.0, < 11.5.20>= 12.0.0, < 12.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed TYPO3 version
    Check the composer.json file in the web root for the 'typo3/cms' version entry, or look for the VERSION file in the TYPO3 core directory, or log into the backend and navigate to Admin Tools > About > Install Tool for version display
    Affected if The version is below 10.4.33, between 11.0.0-11.5.19, or between 12.0.0-12.1.0 (the version falls within one of the affected ranges: <10.4.33, >=11.0.0 <11.5.20, or >=12.0.0 <12.1.1)
  2. Verify password reset functionality is accessible
    Check if the password reset feature is enabled in the TYPO3 installation. For frontend, inspect the site configuration for password reset plugin availability. For backend, confirm the install tool password reset or admin password change capability is present
    Affected if Password reset functionality exists and has been used, creating the condition where sessions should have been revoked but were not
  3. Inspect active frontend sessions
    Query the database table 'fe_sessions' (or equivalent session storage) to list currently active frontend user sessions. Run: SELECT * FROM fe_sessions WHERE ses_iplock = 'ok' AND ses_tstamp > (UNIX_TIMESTAMP() - 3600)
    Affected if Active frontend sessions exist in the database after a password reset has occurred - these sessions would not have been properly invalidated in a vulnerable version
  4. Inspect active backend sessions
    Query the database table 'be_sessions' (or equivalent session storage) to list currently active backend user sessions. Run: SELECT * FROM be_sessions WHERE ses_iplock = 'ok' AND ses_tstamp > (UNIX_TIMESTAMP() - 3600)
    Affected if Active backend sessions exist in the database after a password reset has occurred - these sessions would not have been properly invalidated in a vulnerable version

You are affected if your TYPO3 installation version falls within the affected ranges AND password reset has been used while sessions remain active in the database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.4.33 / 11.5.20 / 12.1.1 or later
Fixed in 10.4.3311.5.2012.1.1
Interim mitigation

Upgrade to TYPO3 versions 10.4.33, 11.5.20, or 12.1.1. Alternatively, manually invalidate all active sessions for affected users via the backend until patching is possible.

Recommended fix High confidence

Upgrade to TYPO3 10.4.33 (if on v10), 11.5.20 (if on v11), or 12.1.1 (if on v12)

  1. 1. Backup your TYPO3 installation and database before proceeding with any upgrade.
  2. 2. Determine your current TYPO3 version by checking the typo3/sysext/core/composer.json or the Install Tool.
  3. 3. If running version 10.x (10.0.0 through 10.4.32), upgrade to version 10.4.33.
  4. 4. If running version 11.x (11.0.0 through 11.5.19), upgrade to version 11.5.20.
  5. 5. If running version 12.x (12.0.0 through 12.1.0), upgrade to version 12.1.1.
  6. 6. Use Composer to update: 'composer require typo3/cms-core:^10.4.33 --with-all-dependencies' (or appropriate version for your branch).
  7. 7. Clear all caches after upgrade via Install Tool or CLI: 'vendor/bin/typo3 cache:flush'.
  8. 8. Verify the upgrade was successful and test password reset functionality to confirm sessions are now properly revoked.
Caveat Patch releases within the same minor version typically have minimal breaking changes; however, always review release notes before upgrading across minor versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23502 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data