Ok, I found a solution by myself - direct manipulation of the field expiry_date in the SQL database table "subscription" and then the automatic mass expiration. But I question myself if this could lead over time to a corruption of the CBSubs database?
Versions: CB 2.7.2, J 3.10.6