If a database cursor is not closed properly, then it could become accessible to other users while retaining the same privileges that were originally assigned, leaving the cursor "dangling."
Extended description
For example, an improper dangling cursor could arise from unhandled exceptions. The impact of the issue depends on the cursor's role, but SQL injection attacks are commonly possible.
Best practices to prevent this CWE
Phase: Implementation
Close cursors immediately after access to them is complete. Ensure that you close cursors if exceptions occur.