The vulnerability stems from improper error handling in POST request processing for delete operations. Key functions identified:

1. SlingPostServlet.handleOperation - Directly processes the vulnerable :operation parameter
2. SlingPostServlet.handleDelete - Implements the specific vulnerable delete logic
3. AbstractPostOperation.run - Base class where operation execution and session commits occur Exploit analysis shows these functions would appear in stack traces when processing malicious delete requests with :applyTo parameters, as they handle the operation dispatch, path resolution, and session management that leads to information disclosure through uncaught exceptions.