You can't.
The Same Origin Policy is there to stop a website you do not trust that is visited by someone you do trust, from using the visitor's browser to make requests to your server and stealing the data from it.
CORS is there to selectively disable the Same Origin Policy when there are third party websites you do trust with the data.
Neither of them solve the problem that you have users who you trust to change your database, but only through the client side UI you give them.
To solve that problem you need better server side authorisation logic.
To take a simple example, if you have a REST API that lets a user delete a comment by sending its ID then you should also require a username and password (or other form to authentication) to be included in the request which lets you know who is making the request. Once you know who is making the request, you must check that they are authorised to delete the comment. Typically that would be logic like:
if (comment.owner == user || user.has_role("admin")) {
comment.delete();
} else {
response.status.unauthorised();
response.send();
}