How severe is GHSA-9895-53fc-98v2?

No CVSS score has been assigned to GHSA-9895-53fc-98v2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9895-53fc-98v2?

GHSA-9895-53fc-98v2 affects the following packages: typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-9895-53fc-98v2?

Update typo3/cms to 6.2.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9895-53fc-98v2 is resolved across your whole dependency graph.

How do I detect GHSA-9895-53fc-98v2 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9895-53fc-98v2 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-9895-53fc-98v2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9895-53fc-98v2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-9895-53fc-98v2 published, and has it been updated?

GHSA-9895-53fc-98v2 was published on June 3, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

TYPO3 SQL Injection in dbal

Real-World Exposure

1 pkg affected

🐘typo3/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

A flaw in the database escaping API results in a SQL injection vulnerability when extension dbal is enabled and configured for MySQL passthrough mode in its extension configuration. All queries which use the DatabaseConnection::sql_query are vulnerable, even if arguments were properly escaped with DatabaseConnection::quoteStr beforehand.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 6.2.0&&< 6.2.18	6.2.18`composer require typo3/cms:^6.2.18`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms to 6.2.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9895-53fc-98v2 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

A flaw in the database escaping API results in a SQL injection vulnerability when extension dbal is enabled and configured for MySQL passthrough mode in its extension configuration. All queries which use the DatabaseConnection::sql_query are vulnerable, even if arguments were properly escaped with DatabaseConnection::quoteStr beforehand.

O3 Security · Impact-Aware SCA

Is GHSA-9895-53fc-98v2 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

TYPO3 SQL Injection in dbalGHSA-9895-53fc-98v2