TYPO3CMS

CVE-2015-8760

MEDIUM · 6.1 CVSS v3.0 Published 2016-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The Flvplayer component in TYPO3 6.2.x before 6.2.16 allows remote attackers to embed Flash videos from external domains via unspecified vectors, aka "Cross-Site Flashing."

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 · high confidence

Cross-Site Flashing (XSF) vulnerability in the Flvplayer component of TYPO3 6.2.x allows remote attackers to embed Flash videos from external domains without proper origin validation. This could enable injection of malicious Flash content to steal session cookies, perform actions as the authenticated user, or redirect users to malicious sites.

MitigationUpgrade TYPO3 to version 6.2.16 or later which contains the patch for this vulnerability. Alternatively, if the Flvplayer component is not required, disable or remove it entirely.

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
Affected:= 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.10

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed TYPO3 version
    Locate the TYPO3 version file (typo3/sources/typo3/VERSION) or check the version in the TYPO3 backend under Admin Tools > About. Alternatively, check typo3/sources/typo3/VERSION and typo3/sources/typo3/CLASSES if present.
    Affected if The installed version is 6.2.0 through 6.2.10 (any version in the 6.2.x range up to 6.2.10)
  2. Verify Flvplayer extension presence
    Check if the Flvplayer extension is installed by examining the typo3conf/ext/ directory for a flvplayer folder, or access the TYPO3 Extension Manager and look for flvplayer in the list of installed extensions.
    Affected if The Flvplayer extension is present in typo3conf/ext/ or shows as installed in the Extension Manager
  3. Confirm Flvplayer is actively used
    Check the TYPO3 backend for pages or content elements that use the Flvplayer plugin. Inspect any FlexForm configurations or tt_content records where plugin.tx_flvplayer is referenced, or look for flvplayer typoscript templates included in the site.
    Affected if Flvplayer is actively loaded or referenced in the site's configuration or content
  4. Inspect Flash embedding configuration
    Examine the Flvplayer extension's configuration files (typically in typo3conf/ext/flvplayer/) for allowDomain or similar settings that control external Flash embedding, or check if the extension's player template allows arbitrary SWF sources.
    Affected if The Flvplayer component allows external domain sources without explicit whitelist restrictions

You are affected if your TYPO3 installation is version 6.2.0-6.2.10 AND the Flvplayer extension is installed and actively used on your site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade TYPO3 to version 6.2.16 or later which contains the patch for this vulnerability. Alternatively, if the Flvplayer component is not required, disable or remove it entirely.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-8760 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-8760 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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