Security issues in WP Forum fixed

All security issues in this report is fixed
.

New version is 1.7.6

Excerpt from the report

Description:
Some vulnerabilities have been discovered in the WP-Forum plugin for WordPress, which can be exploited by malicious users to conduct script insertion attacks, and by malicious people to conduct cross-site scripting and SQL injection attacks.

1) Input passed to the “user” parameter in the WordPress installation’s index.php script (when “forumaction” is set to “showprofile” and “page_id” to a page with the “” tag) is not properly sanitised before being used in SQL queries
. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.

Successful exploitation of this vulnerability allows e.g. retrieving usernames, password hashes, and e-mail addresses for all users and administrators, but requires knowledge of the database table prefix
.

2) Input passed to the “forum_query” parameter in the WordPress installation’s index.php script (when “forumaction” is set to “search”) is not properly sanitised before being returned to the user

therapy and the subsequent resumption of sexual2. Patient communication. Patients may have concerns viagra generic.

. This can be exploited to execute arbitrary HTML and script code in a user’s browser session in context of an affected site.

Successful exploitation of this vulnerability requires that the target user has valid user credentials.

3) Input passed to the “forumtext” parameter in the WordPress installation’s index.php script (when “forumaction” is set to “post”) is not properly sanitised before being stored. This can be exploited to insert arbitrary HTML and script code, which is executed in a user’s browser session in context of an affected site when the malicious data is viewed.

Successful exploitation of this vulnerability requires that the attacker has valid user credentials
.

The vulnerabilities are confirmed in version 1.7.4 . Other versions may also be affected.

Solution:
Edit the source code to ensure that input is properly sanitised.

Provided and/or discovered by:
1) websec Team
2, 3) FeDeReR and sinner_01