I don't see how this could possibly create security vulnerabilities, unless the profiles are shared with other users.
If they're shared, CSRF vulnerabilities could come up (since CSS can generate GET requests to include images, fonts, other stylesheets etc). They could also use content to trick users into clicking some places, hide important functionality, etc. And, of course, you would have to escape <, >, and possibly & to prevent XSS (if the CSS is embedded in the HTML).
As to libraries to do the sanitation, I'm not aware of any (maybe tidy).
behaviorproperty andexpressionsthat IE allows (both of which initiate javascript), I don't see how css could cause any "security vulnerabilities." So if you filter out (or disallow input of) those, I think you would be okay.javascript:URLs in everything that acceptsurl(). Layout hacks to position other content over the top of a login form,@importto bring in an unchecked external file that the author might sabotage later. CSS isn't really that safe.