Richard Lundeen

Name of the Vulnerable Software and Affected Versions: Ektron Content Management System (CMS) versions prior to 8.02 SP5 Description: The issue allows remote attackers to read arbitrary files and consequently bypass authentication, modify viewstate, cause a denial of service, or possibly have unspecified other impact via crafted XSL data. This is due to the XSLTCompiledTransform function configuring the XSL with enableDocumentFunction set to true. Recommendations: For versions prior to 8.02 SP5, update to version 8.02 SP5 or later to resolve the issue. As a temporary workaround, consider disabling the XSLTCompiledTransform function until a patch is available. Restrict access to sensitive files and directories to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** DotNetNuke versions 6.x through 6.0.2 **Description** A cross-site scripting issue allows user-assisted remote attackers to inject arbitrary web script or HTML via a crafted URL containing text that is used within a modal popup. **Recommendations** For versions 6.x through 6.0.2, update to a version that contains a fix for this issue to prevent exploitation.

**Name of the Vulnerable Software and Affected Versions** DotNetNuke versions prior to 5.6.4 DotNetNuke versions 6.x prior to 6.1.0 **Description** A cross-site scripting (XSS) issue exists in the telerik HTML editor, allowing remote attackers to inject arbitrary web script or HTML via a message. **Recommendations** For versions prior to 5.6.4, update to version 5.6.4 or later. For versions 6.x prior to 6.1.0, update to version 6.1.0 or later.

**Name of the Vulnerable Software and Affected Versions** WordPress versions 3.1 through 3.1.2 WordPress versions 3.2 before Beta 2 **Description** The issue allows remote attackers to obtain sensitive data via vectors related to wp-includes/post.php, specifically by treating unattached attachments as published. **Recommendations** For WordPress versions 3.1 through 3.1.2, update to version 3.1.3 or later. For WordPress versions 3.2 before Beta 2, update to Beta 2 or later.

**Name of the Vulnerable Software and Affected Versions** WordPress versions 3.1 through 3.1.2 WordPress versions 3.2 before Beta 2 **Description** The issue is related to "Various security hardening" and has an unknown impact and attack vectors. **Recommendations** For WordPress versions 3.1 through 3.1.2, update to version 3.1.3 or later. For WordPress versions 3.2 before Beta 2, update to Beta 2 or later.

**Name of the Vulnerable Software and Affected Versions** WordPress versions 3.1 through 3.1.2 WordPress versions 3.2 before Beta 2 **Description** The issue is related to "Taxonomy query hardening" and may involve SQL injection, although the exact impact and attack vectors are not specified. **Recommendations** For WordPress versions 3.1 through 3.1.2, update to version 3.1.3 or later. For WordPress versions 3.2 before Beta 2, update to Beta 2 or later.

**Name of the Vulnerable Software and Affected Versions** WordPress versions 3.1 through 3.1.2 WordPress versions 3.2 before Beta 2 **Description** The file upload functionality has unknown impact and attack vectors, possibly related to dangerous filenames, when running on hosts with dangerous security settings. **Recommendations** For WordPress versions 3.1 through 3.1.2, update to version 3.1.3 or later. For WordPress versions 3.2 before Beta 2, update to Beta 2 or later.

**Name of the Vulnerable Software and Affected Versions** WordPress versions 3.1 through 3.1.2 WordPress versions 3.2 before Beta 2 **Description** The issue allows remote attackers to determine usernames of non-authors via canonical redirects. **Recommendations** For WordPress versions 3.1 through 3.1.2, update to version 3.1.3 or later. For WordPress versions 3.2 before Beta 2, update to Beta 2 or later.

**Name of the Vulnerable Software and Affected Versions** WordPress versions 3.1 through 3.1.2 WordPress versions 3.2 before Beta 2 **Description** The issue allows remote attackers to conduct clickjacking attacks via a crafted web site, as it does not prevent rendering for admin or login pages inside a frame in a third-party HTML document. **Recommendations** For WordPress versions 3.1 through 3.1.2, update to version 3.1.3 or later. For WordPress versions 3.2 before Beta 2, update to Beta 2 or later.