dbcve.org
TYPO3CMS

CVE-2025-47937

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-20
Fix available
A fix is available. Upgrade to 9.5.51 / 10.4.50 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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. Starting in version 9.0.0 and prior to versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, and 13.4.12 LTS, when performing a database query involving multiple tables through the database abstraction layer (DBAL), frontend user permissions are only applied via `FrontendGroupRestriction` to the first table. As a result, data from additional tables included in the same query may be unintentionally exposed to unauthorized users. Users should update to TYPO3 version 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS to fix the problem.

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

In TYPO3's database abstraction layer (DBAL), when performing multi-table queries, the FrontendGroupRestriction permission filter is only applied to the first table in the query. This causes unauthorized exposure of data from additional joined tables to frontend users who should not have access to that data.

MitigationUpdate TYPO3 to version 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS or later to receive the fix.

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:>= 9.0.0, < 9.5.51>= 10.0.0, < 10.4.50>= 11.0.0, < 11.5.44>= 12.0.0, < 12.4.31>= 13.0.0, < 13.4.12

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Check TYPO3 core version
    In the TYPO3 admin panel, go to 'About' > 'Install Tool' or check the file typo3/sysext/core/Classes/Information/Typo3Version.php. Alternatively, run: composer show typo3/cms-core | grep version
    Affected if The installed version falls within one of these ranges: >=9.0.0,<9.5.51 OR >=10.0.0,<10.4.50 OR >=11.0.0,<11.5.44 OR >=12.0.0,<12.4.31 OR >=13.0.0,<13.4.12
  2. Verify DBAL extension is installed
    Check for typo3/sysext/dbal in the vendor directory or in TYPO3's extension manager. Run: ls -la typo3/sysext/dbal/ or check composer.json for 'typo3/cms-dbal'
    Affected if DBAL (Database Abstraction Layer) extension is installed and enabled
  3. Identify multi-table queries with frontend group restrictions
    Review application code for queries using QueryBuilder that join multiple tables and apply FrontendGroupRestriction. Search for patterns like $queryBuilder->getRestrictions()->add(new FrontendGroupRestriction()) used with JOIN operations.
    Affected if The application performs multi-table (JOIN) queries that apply FrontendGroupRestriction to filter frontend user permissions
  4. Check if frontend user groups restrict data access
    In TYPO3 backend, go to 'User Management' > 'Frontend User Groups' and verify which tables have group-based access restrictions configured. Also check TCA configuration for 'enablecolumns' => 'fe_group'
    Affected if Tables involved in multi-table queries have frontend group access restrictions configured (fe_group column)

You are affected if TYPO3 version is within the vulnerable ranges AND DBAL is in use AND your application performs multi-table queries with FrontendGroupRestriction applied, causing joined table data to bypass group-based access controls.

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 9.5.51 / 10.4.50 / 11.5.44 or later
Fixed in 9.5.5110.4.5011.5.44
Interim mitigation

Update TYPO3 to version 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS or later to receive the fix.

Recommended fix High confidence

Upgrade to TYPO3 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS (depending on your major version branch)

  1. 1. Create a complete backup of the database and all website files
  2. 2. Test the upgrade in a staging/development environment first
  3. 3. Update TYPO3 using Composer: `composer require typo3/cms-core:^12.4.31 --no-interaction` (adjust the version constraint for your major version branch)
  4. 4. Run database migrations if prompted: `php bin/typo3cms database:updateschema`
  5. 5. Clear all caches: `php bin/typo3cms cache:flush`
  6. 6. Verify the frontend and backend functionality
  7. 7. Confirm that multi-table DBAL queries now properly apply FrontendGroupRestriction to all tables
Caveat TYPO3 major version upgrades may introduce breaking changes; review TYPO3 change logs and test thoroughly before deploying to production

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

Fix this in TYPO3 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47937 — 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-2025-47937 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