WordPress has always taken security very seriously. When identifiable security risks have been found, the developers and community at large have always stepped up to the plate to address the issue.
Recently, a non-critical (though significant) security risk was brought to our attention. A potential solution has been proposed, but it's novel enough that we'd like to get as many people as possible to review it and make sure it's up to WordPress' high security standards.
But why stop with just one cog in the machine? This week, we'd like to step back and make sure everything is still up to snuff, so we're calling all you security minded folk out to help us ensure that the WordPress code is at its best.
We're asking people to assign themselves one (or multiple!) files to audit.
You'll need to go through the file (yup, line by line) to find any potential security holes. Of course, most of WordPress' files reference other files (either directly or through function calls), so you'll need to see how your file talks to others and how other files talk to yours. Sounds awesome, doesn't it? We like to think of it as "Spring Break, WordPress!"
So sign up below by putting your name in parentheses next to the file you'll be working on. If you think everything's hunky-dory, check it off by writing down an "OK".
If you spot a hole or come across something you'd like to discuss, create a new ticket on http://trac.wordpress.org and site the ticket here in your parentheses. Make sure the ticket name and description are well thought out and please tag your ticket with "security-week".
Ideally, each file below will have several people looking it over.
Get testing!
A list of all non image files.
wordpress:
wordpress/wp-admin:
wordpress/wp-admin/images: wordpress/wp-admin/import:
wordpress/wp-content:
wordpress/wp-content/plugins:
wordpress/wp-content/plugins/akismet:
wordpress/wp-content/themes: wordpress/wp-content/themes/classic:
wordpress/wp-content/themes/default:
wordpress/wp-content/themes/default/images:
wordpress/wp-includes:
wordpress/wp-includes/images: wordpress/wp-includes/images/smilies: wordpress/wp-includes/js:
wordpress/wp-includes/js/tinymce:
wordpress/wp-includes/js/tinymce/langs:
wordpress/wp-includes/js/tinymce/plugins: wordpress/wp-includes/js/tinymce/plugins/autosave:
wordpress/wp-includes/js/tinymce/plugins/autosave/langs:
wordpress/wp-includes/js/tinymce/plugins/directionality:
wordpress/wp-includes/js/tinymce/plugins/directionality/images: wordpress/wp-includes/js/tinymce/plugins/directionality/langs:
wordpress/wp-includes/js/tinymce/plugins/inlinepopups:
wordpress/wp-includes/js/tinymce/plugins/inlinepopups/css:
wordpress/wp-includes/js/tinymce/plugins/inlinepopups/images: wordpress/wp-includes/js/tinymce/plugins/inlinepopups/jscripts:
wordpress/wp-includes/js/tinymce/plugins/wordpress:
wordpress/wp-includes/js/tinymce/plugins/wordpress/images: wordpress/wp-includes/js/tinymce/plugins/wordpress/langs:
wordpress/wp-includes/js/tinymce/plugins/wphelp:
wordpress/wp-includes/js/tinymce/plugins/wphelp/images: wordpress/wp-includes/js/tinymce/plugins/wphelp/langs:
wordpress/wp-includes/js/tinymce/themes: wordpress/wp-includes/js/tinymce/themes/advanced:
wordpress/wp-includes/js/tinymce/themes/advanced/css:
wordpress/wp-includes/js/tinymce/themes/advanced/images: wordpress/wp-includes/js/tinymce/themes/advanced/images/xp: wordpress/wp-includes/js/tinymce/themes/advanced/jscripts:
wordpress/wp-includes/js/tinymce/themes/advanced/langs:
wordpress/wp-includes/js/tinymce/utils: