Okay, I'm going to say that you're working against the database in this case. Why store it like that when you can just create another table (a lookup table) to use as the intermediary between your users table and the articles table. Then you can query for info from the articles table and users table and join them on the user_to_article table (as my example above). This would work out better for you in the long run (including when users add or remove or update saved articles 😉 Trust me, I tried this once, and it didn't work out too well).
However, if you want to keep it that way, you could just query the database like so:
SELECT a.*
FROM `articles` AS a
WHERE a.`id`IN (...)
The "..." would be replaced by the string in your saved column 😉