What Denny is saying is the SQL Server service account or the SA account both have SysAdmin rights. If your user connects to SQL with either of these logins, he / she will be able to execute xp_cmdshell and will have SysAdmin rights.
You can make the user account a non-Sysadmin user account and as long as this user doesn't have the pwd to either of the above accounts, you'll be fine. If that user DOES have the pwd to either of the above account, I would advise changing that password and then checking all jobs, replication setups, and SQL Server to SQL Server connections to change the passwords there too.
Catadmin - MCDBA, MCSA
Beware the error of pre-emptive poultry inventory!