An authenticated exploit path is a route through a vulnerability that generally requires the attacker to sign in with a valid account before reaching the vulnerable functionality. The account may have limited permissions; the risk depends on what actions the application allows that user to perform.
This distinction helps defenders assess exposure: a flaw may be harder to exploit if an attacker must first obtain credentials, but authentication does not make it harmless. Review which users can reach the affected feature, restrict access, and apply security updates. Some vulnerabilities also have a separate unauthenticated path, so do not assume that login requirements block every route. In a CMS, modules or custom code can make vulnerable functionality reachable in ways that vary between sites.