exploit the possibilities

TinyMCE 3.5.8 Cross Site Scripting

TinyMCE 3.5.8 Cross Site Scripting
Posted Mar 11, 2013
Authored by Justin C. Klein Keane, Zach Alexander

TinyMCE version 3.5.8 suffers from a cross site scripting vulnerability.

tags | exploit, xss
advisories | CVE-2012-4230
MD5 | c4415aebe3b26671b5804c094eba8298

TinyMCE 3.5.8 Cross Site Scripting

Change Mirror Download
Vulnerability Report

Author: Justin C. Klein Keane <justin@madirish.net>
Date: 5 March, 2013


Description of Vulnerability:
"TinyMCE in itself can not be insecure"

"TinyMCE is a platform independent web based Javascript HTML WYSIWYG
editor control released as Open Source under LGPL by Moxiecode Systems
AB. TinyMCE has the ability to convert HTML TEXTAREA fields or other
HTML elements to editor instances. TinyMCE is very easy to integrate
into other Content Management Systems." (http://www.tinymce.com/)
TinyMCE is widely utilized in a number of web application systems.

A cross site scripting (XSS), or arbitrary script injection,
vulnerability exists in TinyMCE due to the fact that the bbcode plugin
violates the explicit security policy of TinyMCE. If the bbcode plugin
is enabled, but encoding is enabled using the "encoding" directive, or
sanitizing is enabled using the "valid_elements" attribute, these
mechanisms fail to function as expected. According to the "encoding"
documentation: "Posted content will be converted to an XML string
escaping characters such as <, >, ", and & to <, >, ", and
&." (http://www.tinymce.com/wiki.php/Configuration:encoding)
According to the "valid_elements" attribute documentation:
"valid_elements option defines which elements will remain in the edited
text when the editor saves. You can use this to limit the returned HTML
to a subset."
(http://www.tinymce.com/wiki.php/Configuration:valid_elements) However,
if the bbcode plugin is enabled these stated functions do not affect

Systems affected:
TinyMCE 3.5.8 was tested and found vulnerable using Chrome Version

Systems using TinyMCE could erroneously assume a level of protection
against arbitrary script execution within the client side context of
TinyMCE. This could allow attackers to misuse TinyMCE enabled
applications to carry out arbitrary script injection (XSS) attacks.
Victims could be subject to credential theft, client side attack, or
other dangerous condition.

Mitigating factors:
The TinyMCE system must be configured to use the bbcode plugin (included
in TinyMCE).

Proof of Concept Exploit:
Configuring a TinyMCE textarea using:

mode : "textareas",
encoding : "xml",
plugins : "preview",
theme_advanced_buttons1 : "preview,code",
valid_elements : "br,strong",

will create the expected text area. If a user types HTML tags directly
into the textarea then presses the 'Preview' button the HTML characters
are properly encoded and show up in the display. Similarly, if the
'Code' button is pressed the pop up will show encoded HTML entities.

However, if the bbcode plugin is utilized then this behavior changes,
and HTML elements are not encoded, causing HTML tags to be rendered.

The explicit security policy of TinyMCE indicates that if the "encoding"
option is set then HTML entities will be encoded and if the
"valid_elements" option is set HTML elements will be removed, however,
the use of the bbcode plugin overrides this behavior, which could lead
to vulnerabilities in situations where a developer improperly assumed
that HTML would be encoded by the TinyMCE editor.

Steps to Reproduce:
Install TinyMCE and create a textarea with the following init:

mode : "textareas",
encoding : "xml",
plugins : "preview",
theme_advanced_buttons1 : "preview,code",
valid_elements : "br,strong",

Load the page containing the textarea in a browser and enter the text
"<b>test</b>" then click the HTML Source Editor button and note that the
HTML entities are encoded showing "<b>test</b>". Next
change the init to the following:

mode : "textareas",
encoding : "xml",
plugins : "bbcode,preview",
theme_advanced_buttons1 : "preview,code",
valid_elements : "br,strong",

Type "<b>test</b>" into the textarea and again, click the HTML Source
Editor button. Note that the HTML entities have not been encoded. This
test can be run using the text "<script>alert('xss');</script>" for a
more dramatic demonstration of the issue.

This issue was originally discovered by Zach Alexander

Vendor Response:
Vendor has been alerted to this vulnerability but does not consider it a
critical security issue and will look into mitigation at some future time.

Justin C. Klein Keane


RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

File Archive:

June 2019

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Jun 1st
    1 Files
  • 2
    Jun 2nd
    2 Files
  • 3
    Jun 3rd
    19 Files
  • 4
    Jun 4th
    21 Files
  • 5
    Jun 5th
    15 Files
  • 6
    Jun 6th
    12 Files
  • 7
    Jun 7th
    11 Files
  • 8
    Jun 8th
    1 Files
  • 9
    Jun 9th
    1 Files
  • 10
    Jun 10th
    15 Files
  • 11
    Jun 11th
    15 Files
  • 12
    Jun 12th
    15 Files
  • 13
    Jun 13th
    8 Files
  • 14
    Jun 14th
    16 Files
  • 15
    Jun 15th
    2 Files
  • 16
    Jun 16th
    1 Files
  • 17
    Jun 17th
    18 Files
  • 18
    Jun 18th
    0 Files
  • 19
    Jun 19th
    0 Files
  • 20
    Jun 20th
    0 Files
  • 21
    Jun 21st
    0 Files
  • 22
    Jun 22nd
    0 Files
  • 23
    Jun 23rd
    0 Files
  • 24
    Jun 24th
    0 Files
  • 25
    Jun 25th
    0 Files
  • 26
    Jun 26th
    0 Files
  • 27
    Jun 27th
    0 Files
  • 28
    Jun 28th
    0 Files
  • 29
    Jun 29th
    0 Files
  • 30
    Jun 30th
    0 Files

Top Authors In Last 30 Days

File Tags


packet storm

© 2019 Packet Storm. All rights reserved.

Security Services
Hosting By