We just learned of a reflected XSS vulnerability in WordPress 3.3 via the comments form (wp-comments.php). It is explained in detail here.
The disclosed vulnerability can only be triggered via Internet Explorer according to the disclosing party, our tests lead to the same result.
To further note, this is hard to reproduce because it does not get triggered when WordPress is installed via a domain. If you’re running WordPress 3.3, and WordPress was installed via a domain, you’re not vulnerable. (ethicalhack3r)
We do not consider this to be a serious vulnerability, however, we recommend updating to WordPress 3.3.1 since the vulnerability can be used in targeted attacks. More info on the release can be found in the WordPress Codex, over via the release post.
Cesar Anjos
John Castro
Ben Martin
Rianna MacLeod
Nathan Chaddock
Luke Leal
Marc-Alexandre Montpas
Fernando Barbosa
8 comments
I have to ask now. “via a domain”?
Hey Mika, this should clear it up a bit – http://www.ethicalhack3r.co.uk/security/wordpress-3-3-cross-site-scripting-xss/
If your site is accessible by IP vs. Domain you are vulnerable.
Most of the plugins I’m having are infected with malware affecting .js javascript files… the scanner can’t detect it.
I fell very much greatfull for your kind information related to this subject.It makes me aware about this matter.your article related to this matter is very much informative and up to date.
http://www.smtrafficguru.com
Gracias por la informacion 🙂
Comments are closed.