Assuming that your CSV file has combinations of:
comma separated fields (that part is fine)
Some columns wrapped with double-quotes (because they contain a comma)
Some columns, additionally, containing doubled-up-quotes - because they are wrapped with double-quotes but, themselves, include a double quote
then I reckon that all bets are off trying to use BCP to import that.
Also if any field contains an embedded line-break, or if any rows have fewer comma delimiters (e.g. because the trailing fields are all "empty")
IME all these things are common (and, indeed, acceptable) in CSV files. Unfortunately they are not (AFAIK) supported by BCP - why? I don't know, its 20 years since I started using BCP, files using CSV are commonplace and the standard is well understood, short of using XML or binary/Native mode files there isn't a suitable alternative (and CSV is no use for fields with embedded line breaks, nor is any other simple-text file format). Microsoft should have fixed all this decades ago ...
If the file's fields are delimited with comma, there are NO wrapping-double-quotes and NO field has an embedded comma, NO embedded line breaks, then you are probably fine.
You also need that the target import table has columns in identical sequence to the CSV file
If you have any of the wrapper-quotes / embedded commas / short-rows problems then the only way that I know is to use BCP to import to a temporary table, treating each row as a SINGLE column, and then "splitting" the rows, into multiple columns, using SQL. This allows a lot of flexibility - e.g. columns NOT in the same sequence as the target table, and you could probably even handle embedded line breaks.
I always use these parameters to store as much output / debug information as possible. BCP won't necessarily abort on error, and these output files may be the only after-the-fact clue that you get that an unattended batch operation has gone haywire!
-m 1000 (or bigger)
-b (Suitable Batch Size value)
-w if you have Wide characters
-E if you have Identity column
-F if your first row contains column names (Case sensitive)