🛡️ CVE-2010-3662 — cms-backend

🟠 CVSS 8.0 — High ✅ No Known Exploit CWE-89 OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

TYPO3 SQL injection vulnerability on the backend

TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 allows SQL Injection on the backend.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

Weakness class

CVE-2010-3662 is classified as CWE-89: SQL Injection. Untrusted input is concatenated into an SQL statement, letting an attacker change the query and reach data the request should not return.

Affected software

CVE-2010-3662 is recorded against 1 package.

  • typo3/cms-backend (from 4.4.0 up to 4.4.1)

Timeline and source

Published on 21 April 2022 and last revised on 7 February 2024. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Advisory)
bugs.debian.org (Web)
github.com (Package)
security-tracker.debian.org (Web)
typo3.org (Web)

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE CWE-89
Public Exploit ✅ No
Source OSV
Published 2022-04-21
Updated 2026-08-12
Modified 2024-02-07
Fix URL N/A

Affected Packages

Software From version Fixed in
typo3/cms-backend 4.4.0 4.4.1

Similar Threats

Site Security Check

Is cms-backend part of your stack?

CVE-2010-3662 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.