---
title: "TYPO3-CORE-SA-2016-020: Cross-Site Scripting in third party library mso/idna-convert"
url: "https://news.typo3.com/security/advisory/typo3-core-sa-2016-020"
description: It has been discovered, that TYPO3 ships example code of mso/idna-convert library that is vulnerable to Cross-Site Scripting
image: "https://news.typo3.com/_assets/d1e01514e4c4a5b3147940fa2ec50682/Images/og-image-news.jpg"
date: 2026-06-11
modified: 2026-06-11
categories:
  - "Product Updates & Roadmap"
  - TYPO3 CMS
---

# TYPO3-CORE-SA-2016-020: Cross-Site Scripting in third party library mso/idna-convert

- [Product Updates & Roadmap](https://news.typo3.com/article/category/product-updates-roadmap)
- Security / [TYPO3 CMS](https://news.typo3.com/article/category/security/typo3-cms)

TYPO3-CORE-SA-2016-020: Cross-Site Scripting in third party library mso/idna-convert
====================================================================================

19 July 2016

![A laptop screen displaying a list of security advisories](https://news.typo3.com/typo3temp/assets/_processed_/d/c/csm_security_blog_default_77f8e86036.webp)

It has been discovered, that TYPO3 ships example code of mso/idna-convert library that is vulnerable to Cross-Site Scripting

- ![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/7569d41262328e5ed8d27b53e03970ec.png)[Helmut Hummel](https://news.typo3.com/article/author/helmut-hummel)

**Component Type:** TYPO3 CMS

**Release Date:** July 19, 2016

**Vulnerability Type:** Cross-Site Scripting

**Affected Versions:** 7.6.0 to 7.6.9 and 8.0.0 to 8.2.0

**Severity:** Low

**Suggested CVSS v2.0:** [AV:N/AC:L/Au:S/C:N/I:P/A:N/E:F/RL:O/RC:C](http://jvnrss.ise.chuo-u.ac.jp/jtg/cvss/cvss2.cgi?vector=%28AV:N/AC:L/Au:S/C:N/I:P/A:N/E:F/RL:O/RC:C%29&g=2&lang=en)

**CVE:**  not assigned yet

**Problem Description:** TYPO3 ships example code from mso/idna-convert library in the vendor folder, which is vulnerable to Cross-Site Scripting.

**Solution:** Update to TYPO3 versions 7.6.10 or 8.2.1 that fix the problem described.

**Alternative Solution:** Make sure to not expose the vendor directory to the publicly accessible document root. In composer managed installation, make sure to configure a dedicated web folder. In general it is recommended to not expose the complete typo3\_src sources folder in the document root.

**Credits:** Thanks to Frank Huber who discovered and reported the issue.

**General Advice:** Follow the recommendations that are given in the [TYPO3 Security Guide](http://docs.typo3.org/typo3cms/SecurityGuide/ "Opens external link in new window"). Please subscribe to the [typo3-announce](http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-announce) mailing list.

**General Note:** All security related code changes are tagged so that you can easily look them up on our [review system](https://review.typo3.org/#/q/status:merged+project:Packages/TYPO3.CMS+topic:security,n,z).

![](https://news.typo3.com/typo3temp/assets/t3g/blog/gravatar/bb9efc51bced8582e7b8c235f4b5f2b5.png)

About the Author

[Helmut Hummel](https://news.typo3.com/article/author/helmut-hummel)

[More posts by this author](https://news.typo3.com/article/author/helmut-hummel)