Wp Mailup: Cross-site scripting
Wp Mailup is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
- Component
- Wp Mailup
- Plugin slug
wp-mailup- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Mar 22, 2013
This CVE was published Mar 22, 2013 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update Wp Mailup to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
ajax.functions.php in the MailUp plugin before 1.3.3 for WordPress does not properly restrict access to unspecified Ajax functions, which allows remote attackers to modify plugin settings and conduct cross-site scripting (XSS) attacks by setting the wordpress_logged_in cookie. NOTE: this is due to an incomplete fix for a similar issue that was fixed in 1.3.2.
NVD vector: AV:N/AC:L/Au:N/C:N/I:P/A:N
Primary and upstream sources
- NVD record for CVE-2013-0731
- Upstream reference osvdb.org
- WordPress upstream reference plugins.trac.wordpress.org
- Upstream reference secunia.com
- WordPress.org plugin page wordpress.org
- Upstream reference securityfocus.com
- Upstream reference exchange.xforce.ibmcloud.com
- Upstream reference osvdb.org
- WordPress upstream reference plugins.trac.wordpress.org
- Upstream reference secunia.com
- WordPress.org plugin page wordpress.org
- Upstream reference securityfocus.com
- Upstream reference exchange.xforce.ibmcloud.com