The vulnerability stems from shared permission caches between object types due to insufficient cache key scoping. Since DataObject::canEdit() is the core method for permission checks and the advisory specifically mentions cache pollution between files/pages, the root cause must be in the permission caching mechanism. The fix would logically involve adding class name context to cache keys in these permission methods, which aligns with common permission caching patterns in SilverStripe's ORM layer.