dbcve.org
TYPO3CMS

CVE-2015-8758

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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
Multiple cross-site scripting (XSS) vulnerabilities in unspecified frontend components in TYPO3 6.2.x before 6.2.16 and 7.x before 7.6.1 allow remote authenticated editors to inject arbitrary web script or HTML via unknown 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 confidence

Multiple cross-site scripting (XSS) vulnerabilities in unspecified frontend components of TYPO3 CMS versions 6.2.x before 6.2.16 and 7.x before 7.6.1 allow remote authenticated editors to inject arbitrary web script or HTML via unknown vectors.

MitigationUpgrade to TYPO3 6.2.16 or 7.6.1 or later which contains the patches, or if upgrade is not feasible, identify and properly sanitize the vulnerable frontend component inputs.

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.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.11

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

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

  1. Determine installed TYPO3 version
    Log into the TYPO3 backend as administrator and navigate to the 'About' module (or check the file typo3/sysext/core/Classes/Information/VersionNumberUtility.php for the version constant), or run: composer show typo3/cms-core 2>/dev/null | grep version
    Affected if Running TYPO3 6.2.0 through 6.2.15, or 7.0 through 7.6.0 (versions before 6.2.16 or 7.6.1)
  2. Confirm TYPO3 branch
    Identify whether the installation is on the 6.2.x LTS branch or the 7.x branch by checking the version number obtained in the previous step
    Affected if Running either the 6.2.x or 7.x branch in the affected version range
  3. Check for active frontend editor accounts
    In TYPO3 backend, go to 'User Admin' > 'Backend Users' and review user records to identify accounts with editor-level privileges (typically 'editor' or 'author' user groups), or query the be_users table in the database for user records with explicit group assignments
    Affected if Any authenticated editor or author user accounts exist in the system
  4. Verify frontend access is enabled
    Check the TYPO3 installation configuration (LocalConfiguration.php or AdditionalConfiguration.php) for enabled frontend-related extensions and the general enableCaching setting; also verify that the frontend is not completely disabled via TSconfig (setup.frontendDisabled)
    Affected if Frontend components and editor access are active, allowing authenticated editors to interact with frontend rendering
  5. Identify frontend editing functionality
    Review installed extensions in the Extension Manager, specifically looking for extensions that provide frontend editing, form handling, or user-generated content rendering; check typo3conf/ext/ for custom or third-party extensions handling frontend input
    Affected if Extensions that provide frontend editing capabilities are installed and enabled

A system is affected if it runs TYPO3 version 6.2.0-6.2.15 or 7.0-7.6.0 with authenticated editor accounts able to access frontend components.

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 to TYPO3 6.2.16 or 7.6.1 or later which contains the patches, or if upgrade is not feasible, identify and properly sanitize the vulnerable frontend component inputs.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-8758 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-8758 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