Salutation Responsive 3.0.15 Cross Site Scripting

Salutation Responsive WordPress + BuddyPress Theme version 3.0.15 suffers from a persistent cross site scripting vulnerability.

MD5 | e2ceef7f36fb6d9e5648cbbf9614ec8b

Software: Salutation Responsive WordPress + BuddyPress Theme
Version: 3.0.15
Advisory report:
CVE: Awaiting assignment
CVSS: 4.9 (Medium; AV:N/AC:M/Au:S/C:P/I:P/A:N)

Stored XSS in Salutation Responsive WordPress + BuddyPress Theme could allow logged-in users to do almost anything an admin can

The theme contains JavaScript (assets/js/onLoad.js) whichA iterates through .section-tabs aA and puts every href value it finds into jQuery(). jQuery() doesnat just search for elements which match a selector (i.e. jQuery(\'.section-tabs\')), it also creates elements (i.e. jQuery(\'<div>\')).

// ...

$.fn.simpleSlideTop = function(opts) {

// ...

contentID = $(this).attr(\'href\');

An attacker without the unfiltered_htmlA capability would be able to inject arbitrary HTML as if they had the unfiltered_htmlA capability.A With the ability to inject arbitrary HTML, the attacker is ableA add JavaScript which causes a logged-in administrator user to do almost anything a including creating new user accounts, deleting posts, and more.

Proof of concept

Click the activate button on the theme
Install and activate Revolution Slider plugin
Create a new user with role ofA Author (by default, Authors do not possess the unfiltered_html capability)
Log in as that user
Visit aAdd New Posta screen
Switch the editor to aTexta mode
Enter the following:A <div class=\"section-tabs\"><a href=\"<img src=x onerror=alert(1)>\">a</a></div>
PressA aPublisha
Press aView posta
You will see an alertbox appear showing the value a1a

For comparison,A if the same user account entersA <img src=x onerror=alert(1)> or <script>alert(1)</script>, it will be blocked by WordPress.

Upgrade to versionA 3.0.16 or later.

Disclosure policy
dxw believes in responsible disclosure. Your attention is drawn to our disclosure policy:

Please contact us on [email protected] to acknowledge this report if you received it via a third party (for example, [email protected]) as they generally cannot communicate with us on your behalf.

This vulnerability will be published if we do not receive a response to this report with 14 days.


2017-04-26: Discovered
2017-07-25: Reported via contact form onA
2017-07-25: Vendor reported issue fixed in 3.0.16
2017-07-31: Advisory published

Discovered by dxw:
Tom Adams
Please visit for more information.

Related Posts