I see there remains much confusion, so I will attempt to break it down into small steps:
1) In the WP Admin Area, only users who have proper permissions are allowed to access the Media Library. By default, this means that the user must be an Author, Editor, or Admin in order to access the Media Library. Subscribers and Contributors, by default, do not have access.
This native WP functionality is by design and ensures that only trusted users with sufficient capabilities are able to access the Media Library.
2) On the front-end, USP uses this native WP functionality to keep things nice and simple:
– Users who are not logged in to WP will not have access to the Media Library
– Logged in Subscribers and Contributors will not have access to the Media Library
– Logged in Authors, Editors, and Admins will have access to the Media Library
So as explained previously, USP works exactly like WP in this regard. Whether or not a user has access to the Media Library depends entirely on their user role (i.e., capabilities).
So if you are registering all of your users as Authors or better, then yeah they are going to have access to the Media Library on the front-end, just as they do when using the Admin Area. And conversely, if you are registering users as Contributors or Subscribers, then they are NOT going to have access to the Media Library. It works exactly like WordPress, regardless of using front-end via USP or backend via the Admin Area.
I hope this makes sense. I’ve tried to explain it as clearly as possible. But I also understand that WordPress is sort of advanced and can be confusing to some people.
Some further points:
– Even if you are registering users as Authors or better, you can disable access to the Media Library at any time by disabling the setting, “Enable Rich Text Editor”. This is an added feature of USP to help folks such as yourself who may not want to give Authors, Editors, and Admins access to the Media Library on the front-end (even though WP still grants them access to the Media Library in the Admin Area).
– If you really felt that this feature of USP was a “serious security issue” (which it is not), why on earth would you post about it publicly and put thousands of sites at risk? And in the “Reviews” section, to boot? Your behavior is not only extremely disrespectful, it goes against official WordPress guidelines:
https://make.www.ads-software.com/core/handbook/testing/reporting-security-vulnerabilities/
I suggest that you take a moment and educate yourself regarding responsible disclosure of suspected security vulnerabilities. And in the future, instead of posting your thoughts publicly, show some respect and concern for others in the WP community and reach out first to the developers, in private, and give them a chance to resolve the issue.