WordPress Mingle Forum Plugin Cross-Site Scripting and SQL
WordPress Mingle Forum Plugin Cross-Site Scripting and SQL Injection Vulnerabilities
Release Date : 2013-02-20
Criticality level : Moderately critical
Impact : Cross Site Scripting
Manipulation of data
Where : From remote
Solution Status : Vendor Patch
Software: WordPress Mingle Forum Plugin 1.x
Description:
Multiple vulnerabilities have been discovered in the Mingle Forum plugin for WordPress, which can be exploited by malicious users to conduct SQL injection attacks and by malicious people to conduct cross-site scripting and SQL injection attacks.
1) Input passed to the "search_words" POST parameter in index.php (when "page_id" is set to a valid forum page id and "mingleforumaction" is set to "search") is not properly sanitised in wp-content/plugins/mingle-forum/wpf.class.php before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
2) Input passed to the "togroupusers" POST parameter in wp-admin/admin.php (when "page" is set to "mfgroups", "usergroup" is set to a valid group ID, and "add_user_togroup" is set) is not properly sanitised in wp-content/plugins/mingle-forum/fs-admin/fs-admin.php before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
3) Input passed via the "id" parameter to index.php (when "page_id" is set to a valid forum page id, "mingleforumaction" is set to "viewtopic", "t" is set to e.g. "1.0", and "remove_post" is set) is not properly sanitised in wp-content/plugins/mingle-forum/wpf.class.php before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
4) Input passed via the "id" parameter to index.php (when "page_id" is set to a valid forum page id, "mingleforumaction" is set to "viewtopic", "t" is set to e.g. "1.0", and "sticky" is set) is not properly sanitised in wp-content/plugins/mingle-forum/wpf.class.php before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
5) Input passed via the "id" parameter to index.php (when "page_id" is set to a valid forum page id, "mingleforumaction" is set to "viewtopic", "t" is set to e.g. "1.0", and "closed" is set) is not properly sanitised in wp-content/plugins/mingle-forum/wpf.class.php before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
6) Input passed via the "thread" parameter to index.php (when "page_id" is set to a valid forum page id and "mingleforumaction" is set to "postreply") is not properly sanitised in wp-content/plugins/mingle-forum/wpf.class.php before being used in a SQL query. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
The vulnerabilities are confirmed in version 1.0.33.3. Prior versions may also be affected.
Solution:
Update to version 1.0.34.
Provided and/or discovered by:
1, 2, 4, 5,6) Secunia Research.
3) Independently discovered by Charlie Eriksen and Secunia Research.
Original Advisory:
Secunia Research:
http://secunia.com/secunia_research/2013-3/
http://secunia.com/secunia_research/2013-4/
http://secunia.com/advisories/52167/
Was this reply helpful? (0) (0)
Staff pick