TYPO3CMS
CVE-2015-8756
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 search result view in the Indexed Search (indexed_search) component in TYPO3 6.2.x before 6.2.16 allows remote authenticated editors to inject arbitrary web script or HTML via unspecified vectors.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in TYPO3's Indexed Search (indexed_search) component's search result view. Authenticated editors with access to the indexed_search functionality can inject malicious web scripts or HTML that persist and execute when other users view search results.
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= 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.10CVSS 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
- 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
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 versionLocate the TYPO3 version number in the admin panel (under Help > About) or in the file typo3/sysext/core/Classes/Core/SystemEnvironmentBuilder.php where the VERSION variable is definedAffected if The version is 6.2.0 through 6.2.15 inclusive (versions below 6.2.16 are affected)
-
Confirm indexed_search extension is installedVerify the indexed_search extension is present and loaded in the TYPO3 extension manager or by checking for the sysext/indexed_search directory in the installationAffected if The indexed_search extension is installed and enabled on the system
-
Verify user access to indexed_searchCheck if authenticated backend users or editors have been granted access to the indexed_search module through the TYPO3 user/group permission settingsAffected if Any editor-level or higher authenticated user has permissions to use the indexed_search functionality, as they would be able to trigger the stored XSS
-
Inspect search result renderingReview the search result template files in sysext/indexed_search/Resources/Private/Language/ or the PHP classes handling result display in sysext/indexed_search/Classes/ to identify where user-supplied search terms are rendered without proper output encodingAffected if Search terms from indexed search results are displayed without sanitization, indicating the vulnerability is present
You are affected if your TYPO3 installation runs version 6.2.0 through 6.2.15 AND has the indexed_search extension enabled, allowing any editor with access to inject persistent scripts into search results.
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 later to receive the security patch for this vulnerability.
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-8756 — 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-8756 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