Was site hacked through wp emoji?

See: http://killmalware.com/eksp.dk/ defacement
See for code: http://www.domxssscanner.com/scan?url=http%3A%2F%2Fwww.eksp.dk

 <script type="text/javascript">
			window._wpemojiSettings = {"baseUrl":"http:\/\/s.w.org\/images\/core\/emoji\/72x72\/","ext":".png","source":{"concatemoji":"http:\/\/www.eksp.dk\/wp-includes\/js\/wp-emoji-release.min.js?ver=4.2.4"}};
			!function(a,b,c){function d(a){var c=b.createElement("canvas"),d=c.getContext&&c.getContext("2d");return d&&d.fillText?(d.textBaseline="top",d.font="600 32px Arial","flag"===a?(d.fillText(String.fromCharCode(55356,56812,55356,56807),0,0),c.toDataURL().length>3e3):(d.fillText(String.fromCharCode(55357,56835),0,0),0!==d.getImageData(16,16,1,1).data[0])):!1}function e(a){var c=b.createElement("script");c.src=a,c.type="text/javascript",b.getElementsByTagName("head")[0].appendChild(c)}var f,g;c.supports={simple:d("simple"),flag:d("flag")},c.DOMReady=!1,c.readyCallback=function(){c.DOMReady=!0},c.supports.simple&&c.supports.flag||(g=function(){c.readyCallback()},b.addEventListener?(b.addEventListener("DOMContentLoaded",g,!1),a.addEventListener("load",g,!1)):(a.attachEvent("onload",g),b.attachEvent("onreadystatechange",function(){"complete"===b.readyState&&c.readyCallback()})),f=c.source||{},f.concatemoji?e(f.concatemoji):f.wpemoji&&f.twemoji&&(e(f.twemoji),e(f.wpemoji)))}(window,document,window._wpemojiSettings);
		</script>  

Read: https://poststatus.com/the-trojan-emoji/
& http://www.bullguard.com/blog/2015/01/emojis-vulnerable-to-hacks-and-a-companys-reputation-destroyed-thanks-to-bugs.html

polonus

it is clean now if you click Killmalware rescan …

Hi Pondus,

Right, that initial defacement has been cleansed. There are serious WP issues with vulnerabilties: Warning User Enumeration is possible
The first two user ID’s were tested to determine if user enumeration is possible.

User ID 1 : admin
User ID 2 : mikael
It is recommended to rename the admin user account to reduce the chance of brute force attacks occurring. As this will reduce the chance of automated password attackers gaining access. However it is important to understand that if the author archives are enabled it is usually possible to enumerate all users within a WordPress installation.

Only the first two user ID’s were tested with this scan, use the Nmap NSE enumeration scripts (use your own Nmap installation or try option 2 below) to discover additional user ID’s.

A fail that could lead to a full deface: http://www.securityfocus.com/archive/1/534250 and it is still there!

Theme vulnerabilty issues: http://theme-fusion.com/avada-documentation/changelog.txt

Hoster has a bad web rep: Zitcom A/S

polonus

Update on such a defacement: http://killmalware.com/airpower.ro/
and WordPress Version
4.4.5
Version does not appear to be latest 4.6.1 - update now.
Content after the < /html> tag should be considered suspicious.
https://aw-snap.info/file-viewer/?tgt=http%3A%2F%2Fwww.airpower.ro%2F&ref_sel=GSP2&ua_sel=ff&fs=1

The proof of the puding is in the eating, well here it is inside this code:
http://www.domxssscanner.com/scan?url=http%3A%2F%2Fwww.airpower.ro%2Fwp-inclues%2Fjs%2Fwp-emoji-release.min.js%3Fver%3D4.4.5d

pol