Skip to main content

WordPress version 4.2 still unsafe.

Most popular WordPress versions are currently affected.

A stored cross-site scripting (XSS) vulnerability available in the recently released WordPress 4.2 and earlier versions can be exploited by an unauthenticated party to run arbitrary code on the server; the security glitch is currently unpatched and proof-of-concept code is publicly available.

An attacker taking advantage of the flaw could take control of the targeted website by creating new admin accounts. Aside from the current WordPress versions, build 4.1.2, 4.1.1 and 3.9.3 are also affected. Comment text truncation issue still not fully fixed.

Discovered by Jouko Pynnönen, from vulnerability research firm Klikki Oy in Finland, the flaw is similar to the one patched in WordPress 4.1.2, after having been disclosed to the developer by researcher Cedric Van Bockhaven about 14 months ago, on February 23, 2014.

Bockhaven’s approach consisted in introducing a character in the message that truncates the text at a specific point, turning it into a script that executes malicious code on the server upon a certain action, such as “mouseover.”

Pynnönen’s method differs only in the way truncation of the text is achieved, which occurs when the comment is stored in the website’s database.

Comments that are larger than 64kb are truncated via MySQL. One way to reach the limit is to paste random characters after the malicious part has been included.

Truncating the messages results in malformed HTML code being generated on the page, which can be leveraged by an attacker to add any attributes in the supported HTML tags and submit malicious JavaScript that delivers a payload.

continue reading at Softpedia.com

Our hosting provider Moscom.com is already applying the latest update to our core content management system. If you haven't done so, check with your hosting provider regarding this vulnerability and ask how they handling to secure (patch) your website.

Source: KING.NET

Comments

Popular posts from this blog

Office365 - This resource doesn't accept meetings longer than 1440 minutes

When you create a meeting schedule for number of days, you will see an error  "This resource doesn't accept meetings longer than 1440 minutes". By default the mailbox or room was set for a maximum limit of 1440 minutes.

Here's how you can disable this limit.
Login to the Office 365 Administration ConsoleIn Microsoft Office 365 Exchange, click on Manage.In Manage My Orgnization, click the drop down arrow, and click on Select on Another User. This will prompt you to select the mailbox or room to manage.Select a Mailbox or Room, click OK.In Option, click on Settings.In Scheduling Options, un-check the "Limit meeting duration", then click on Save. That's all. You can now schedule a meeting or reserve a room for number of days.

Hope this help you.

If this helped you, please take the time to share this post by sharing using Google+, Facebook, Twitter, or LinkedIn

Out of Office Reply for Termed Employee

This is a sample Out of Office message that I used for termed employees, unless HR staff specified a different message.

=== Example for KING.NET Employee ===
John Doe (employee or consultant) is no longer with KING.NET effective June 1, 2013 (termination date). For matters relating to "Project Name here" please direct your concerns to John Smith at johnsmith@king.net (Manager or Supervisor). For all other matters, please direct your email to Mary Smith HR at marysmith@king.net.

Please call our main office 703-345-6789 if you have other concerns.
Thank you.

=== End of message ===

I posted this article year 2008 from my old blog.
http://whaddya.blogspot.com/2008/11/example-of-out-of-office-reply-for.html


If this helped you, please take the time to share this post by sharing using Google+, Facebook, Twitter, or LinkedIn

Facebook Business Valuation

Interesting post from Techcrunch.com about the Facebook valuation and I would like to share this to you folks. The picture graph provide a thousand words to fully explain their growth. Please click the image to see in full screen.