The issue arises from incorrect user permission validation, allowing authenticated users with the maintainer role to modify configurations. This can be exploited through API calls such as PUT /projects/{project name or id}/metadatas/{meta name}, POST /projects/{project name or id}/metadatas/{meta name}, and DELETE /projects/{project name or id}/metadatas/{meta name}. The maintainer role, intended for individuals supporting project admins, can utilize the metadata API to circumvent configuration management limitations. However, the attacker must be authenticated and granted a specific project maintainer role, limiting their scope to that project.