Should I create a new table that would hold my images?
Yes, that's an excellent idea. But don't copy the data from record to record (unless you need a historical record). That dramatically increases the amount of data you have to store. Rather, just reference the image in the images table via an imageID field in your parent table.
You should probably use dedicated ID fields rather than a concatenation of text strings to make the relational join. Otherwise, it presents the possibility of users messing up your joins by entering text strings you didn't anticipate. A value list with the ID and the description of the image can be used to populate it.