http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities Always something worth reading... Fri, 12 Mar 2010 11:09:45 +0000 http://wordpress.org/?v= hourly 1 http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/comment-page-1#comment-8694 WordPress Security - More On Themes And Plugins (ActiveBlogging) Thu, 27 Mar 2008 05:11:32 +0000 http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/#comment-8694 [...] Blogsecurity.net (an excellent security blog and well worth bookmarking) reported on the security flaws of some packages and poorly formed mySQL input. Note this isn’t malicious coding of plugins - it’s just code that hasn’t been checked thoroughly in its inputs. Still, the end result is someone gets access to something they shouldn’t. [...] [...] Blogsecurity.net (an excellent security blog and well worth bookmarking) reported on the security flaws of some packages and poorly formed mySQL input. Note this isn’t malicious coding of plugins – it’s just code that hasn’t been checked thoroughly in its inputs. Still, the end result is someone gets access to something they shouldn’t. [...]

]]> http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/comment-page-1#comment-7788 WordPress Podcast: Episode 34: WordPress 2.3.3 released, more security problems and Prologue | Pittsburgh Punch Wed, 27 Feb 2008 04:59:15 +0000 http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/#comment-7788 [...] array elements could execute unsanitized HTML to exploit the plugin. Other plugins with problems: WordsPew v3.x reported an “id” based SQL injection vulnerability, dmsguestbook 1.7.0, st_newsletter [...] [...] array elements could execute unsanitized HTML to exploit the plugin. Other plugins with problems: WordsPew v3.x reported an “id” based SQL injection vulnerability, dmsguestbook 1.7.0, st_newsletter [...]

]]> http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/comment-page-1#comment-7700 Episode 34: WordPress 2.3.3 released, more security problems and Prologue | PHP Podcasts Tue, 26 Feb 2008 05:16:36 +0000 http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/#comment-7700 [...] array elements could execute unsanitized HTML to exploit the plugin. Other plugins with problems: WordsPew v3.x reported an “id” based SQL injection vulnerability, dmsguestbook 1.7.0, st_newsletter [...] [...] array elements could execute unsanitized HTML to exploit the plugin. Other plugins with problems: WordsPew v3.x reported an “id” based SQL injection vulnerability, dmsguestbook 1.7.0, st_newsletter [...]

]]> http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/comment-page-1#comment-6940 BlogSecurity » Blog Archive » WordPress BlogWatch Sun, 10 Feb 2008 19:01:49 +0000 http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/#comment-6940 [...] SQL Injection Vulnerability (more) [...] [...] SQL Injection Vulnerability (more) [...]

]]> http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/comment-page-1#comment-6911 Pierre Sudarovich Fri, 08 Feb 2008 09:24:44 +0000 http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/#comment-6911 Hi all, ok the bug in wordspew-rss.php is now corrected ;) Hi all,
ok the bug in wordspew-rss.php is now corrected ;)

]]> http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/comment-page-1#comment-6822 DK Tue, 05 Feb 2008 09:40:38 +0000 http://blogsecurity.net/wordpress/dmsguestbook-st_newsletter-wordspew-wp-footnotes-vulnerabilities/#comment-6822 Again, as I stressed before, secure coding functions, documentation and procedures need to be in place before this gets better! Again, as I stressed before, secure coding functions, documentation and procedures need to be in place before this gets better!

]]>