This is possibly an internationalization problem. Many languages use comma and semicolon differently and there are sometimes conflicts.
How big a problem is this for you, though? Most applications that import 'CSV' have options for interpreting the field delimiter. Despite the C meaning 'comma', reality says this can be a variety of characters.
At a pinch, depending on your data, a simple find-and-replace in a text editor may get you your commas, but beware of things like street addresses, which often have a comma between City and State (at least in the US), as well as many European (and other?) languages where a comma is used as a decimal separator (e.g. in US 123.45 would be written as 123,45 in France, and is likely why commas aren't being used as field delimiters in the first place.)
Semi-colons are used far less frequently and is actually a smarter solution in many ways. I bet the original CSV design team are kicking themselves for not thinking of it.