There's a lot to be said about the abuse of or over-dependence on libraries/frameworks but I think it's more related to non-technical factors like hiring practices and time to complete projects. If there's no time to implement something that isn't related to business logic or the person implementing the feature isn't skilled enough to use a bare-bones framework without risking major bugs and security vulnerabilities it would make sense to just use a library/framework that might incur some perf trade-offs. Devs can do a lot to improve their skills but if they don't have time or resources to create a polished product, well, they don't time.

A library can make some huge mistakes for sure (security vulnerabilities, poor optimization, etc.), but how devs use those libraries is more often than not what will lead to major issues.