CVE-2010-3659
TYPO3 Cross-site Scripting vulnerability in the extension manager and backend forms
Overview
Description
Multiple cross-site scripting (XSS) vulnerabilities in TYPO3 CMS 4.1.x 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 allow remote authenticated backend users to inject arbitrary web script or HTML via unspecified parameters to the extension manager, or unspecified parameters to unknown backend forms.
Source: OX vulnerability database
Severity
5.4 · MEDIUM
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Weakness: CWE-79
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Composer (PHP) | typo3/cms-backend | >=4.1.0, <4.1.14>=4.2.0, <4.2.13>=4.3.0, <4.3.4>=4.4.0, <4.4.1 | 4.1.144.2.134.3.44.4.1 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- www.openwall.com http://www.openwall.com/lists/oss-security/2010/09/28/8
- www.openwall.com http://www.openwall.com/lists/oss-security/2014/02/12/8
- www.securityfocus.com http://www.securityfocus.com/bid/42029
- github.com https://github.com/TYPO3-CMS/backend
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2010-3659
- security-tracker.debian.org https://security-tracker.debian.org/tracker/CVE-2010-3659
- security-tracker.debian.org https://security-tracker.debian.org/tracker/CVE-2010-3659/
- typo3.org https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-sa-2010-012
- typo3.org https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-sa-2010-012/
- web.archive.org https://web.archive.org/web/20120903133822/http://www.securityfocus.com/bid/42029
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.