It's a teoretical question.
When say you have some classes and they all call the method com.package.Authentification->isAuthentificated() at the begining(lets really go extreme) of every method in all the classes.
Is the repeating call of that method acros those classes itself a crosscutting-concern? It's something abstract that the programer doesn;t need to know how it works and put "nicely" into an OOP construct, but it doesn;t have nothing to do with the bussines logic of any class, so it would be more logic to not be there at all.
Normally, you could have a module that takes care of authentification that is separate from your business logic. To combine these two modules, it becomes (often) a case of copy-pasting the authentification code into your business logic (and possibly else where). That is a cross-cutting concern, as the authentication concern is present in multiple areas of another concern (business logic in this case).
Yeah, it does seem so. Thanks.