Nope, I suggest creating multiple fields for them to supply this info then output the display using a delimiter field. There's ways to fake a repeating field using CB Auto Actions, but the user won't have a way to edit/delete the old entries.

Sort of, you'd create a new database table to store this information. You'd then create 2 fields for the user to supply the information. Once done you'd create 2 CB Auto Actions. 1 would be a Query action and it'd take the field values after profile update and pass them to the new database table. You'd then have a Field action directly after the query action to reset those fields back to blank. This approach won't allow them to edit the values though.

Easiest approach is to just give them multiple sets of the same fields. For example create 2 fields for the 2 values say 10 times (20 fields). Then use a delimiter field and substitutions to format the output to a single field.