MongoDB integration for Laravel vulnerabilities

Improper neutralization of special elements in data query logic in the cache lock implementation of the MongoDB integration for Laravel can cause a caller-supplied lock owner value to be evaluated as an aggregation expression rather than as a literal value. An authenticated user who can influence the owner value may take over or prematurely expire a lock held by another process, leading to duplicated or conflicting operations.

The MongoDB integration for Laravel contains an improper neutralization of special elements in embedded-document relation handling, where a caller-supplied embedded record identifier can be interpreted as a query condition rather than a literal identifier. An authenticated user who can influence such an identifier may delete all embedded documents in a targeted record or overwrite an embedded document other than the intended target.

Improper neutralization of special elements in data query logic in the MongoDB integration for Laravel can cause an array supplied to an explicit equality filter to be interpreted as a query condition rather than as a literal value. This affects the three-argument `where` method when the operator is `=` or `eq`, as well as the `find` and `delete` methods that use that code path.