Cross-site scripting WordPress (March 7, 2013)

Posted: March 9, 2013 in Vulnerabilities
Tags: , , , ,

Wordpress VulnerabilityVulnerability: Cross-site scripting WordPress Count per Day

Danger level: Low
Patch: None
Number of vulnerabilities: 1

Operation vector: Remote
Impact: Cross Site Scripting

Affected products: WordPress Count per Day Plugin 3.x

Affected versions: WordPress Count per Day 3.2.5, possibly earlier.

Description:

The vulnerability allows malicious people to conduct XSS attacks.

The vulnerability is caused due to insufficient input validation in the parameter “daytoshow” in script wp-content/wp-admin/index.php (when the parameter “page” is “cpd_metaboxes”). This can be exploited to execute arbitrary HTML and script code in a user’s browser session in context of an affected site.

Solution: The way to eliminate the vulnerability does not exist at present.

Links:
http://seclists.org/fulldisclosure/2013/Mar/48

Vulnerability: Cross-site scripting WordPress Events Manager

Danger level: Average
Patch: Yes
Number of vulnerabilities: 3

Operation vector: Remote
Impact: Cross Site Scripting

Affected products: WordPress Events Manager Plugin 5.x

Affected versions: WordPress Events Manager 5.3.5, possibly earlier.

Description:

The vulnerability allows malicious people to conduct XSS attacks.

1. The vulnerability is caused due to insufficient input validation in the parameter “event_owner_name” in the script index.php (when the parameter “action” is “event_save”). This can be exploited to execute arbitrary HTML and script code in a user’s browser session in context of an affected site.

Note: Successful exploitation requires that the page with short code “event_form” was available for unregistered users.

2. The vulnerability is caused due to insufficient input validation in the parameter “dbem_phone” in script wp-admin/admin-ajax.php (when the parameter “action” is “booking_add”). This can be exploited to execute arbitrary HTML and script code in a user’s browser session in context of an affected site.

Note: Successful exploitation requires that the option “No-User Booking Mode” has been disabled, and “bookings for an event” and “guest bookings” were included.

3. The vulnerability is caused due to insufficient input validation in the parameters “event_start_date”, “event_end_date” and “event_rsvp_date” in script wp-admin/post.php (when the parameter “action” is “editpost”, and “post_type” is “event” ). This can be exploited to execute arbitrary HTML and script code in a user’s browser session in context of an affected site.

Solution: Install the latest version 5.3.6 from the manufacturer.

Links:
http://wordpress.org/extend/plugins/events-manager/changelog/
http://plugins.trac.wordpress.org/changeset/674129/events-manager

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s