Licensed module access blocked without active maintenance?

The module continues to inject itself into your call flows. But the web interface is blocked from making changes or viewing current state of the module’s configuration.

The screenshot you provided is missing some important information. What versions of which module(s) are you running and when did the maintenance expire ?

Please refer to the related blog post and associated forum topic from a couple of months ago that introduced the change in behavior: Avoid walking the plank with expired modules

That remains the case for validly licensed commercial modules – you can continue to use any version of the module that was available during your active maintenance period.