TYPO3CMS
CVE-2015-8757
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 · uneditedCross-site scripting (XSS) vulnerability in the Extension Manager in TYPO3 6.2.x before 6.2.16 and 7.x before 7.6.1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors related to extension data during an extension installation.
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 · moderate confidenceXSS vulnerability in TYPO3's Extension Manager allows remote attackers to inject arbitrary web script or HTML via malicious extension data during the extension installation process. The vulnerability affects TYPO3 versions 6.2.x before 6.2.16 and 7.x before 7.6.1.
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
= 6.2.0= 6.2.1= 6.2.2= 6.2.3= 6.2.4= 6.2.5= 6.2.6= 6.2.7= 6.2.8= 6.2.9= 6.2.10= 6.2.11CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed TYPO3 versionLog into TYPO3 backend and navigate to Help > About, or check the file typo3/sysext/core/Classes/Utility/VersionNumberUtility.php for the VERSION constant, or look for version info in typo3/sysext/core/composer.jsonAffected if Version is 6.2.0 through 6.2.15, or 7.0.0 through 7.6.0
-
Verify Extension Manager is accessibleCheck if the Extension Manager module is enabled in the backend user access rights, or attempt to access the Extension Manager via the backend at Admin Tools > ExtensionsAffected if User has admin access to Extension Manager in affected version range
-
Identify extensions installed during vulnerable periodReview extension installation history in the Extension Manager, or query the database table tx_extensionmanager_domain_model_extension for installation datesAffected if Extensions were installed while running an affected version and the installation process involved third-party or untrusted extension sources
-
Check for suspicious extension recordsQuery the database tables tx_extensionmanager_domain_model_extension and tx_extensionmanager_domain_model_repository for extensions with unusual names, unexpected installation dates, or suspicious metadataAffected if Unknown or unexpected extensions are present in the database with installation dates corresponding to the affected version period
You are affected if your TYPO3 installation runs version 6.2.0-6.2.15 or 7.0.0-7.6.0 AND you have used the Extension Manager to install extensions during that time.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade TYPO3 to version 6.2.16 or 7.6.1 or later to resolve the vulnerability. Review and validate any extension installations performed during the affected timeframe.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8757 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-8757 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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