Mercator has a Personal Identifiable Information Leak from Query Executor feature
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 0.4%
from disclosure to weapon0 days
Published on NVDJun 19
1st PoCMay 27
exploitation probability
0.4%top 69% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
Mercator is an open source web application that enables mapping of the information system. Prior to version 2025.05.19, Mercator's Query Engine (`/admin/queries/execute`) accepts a JSON DSL (`from` / `select` / `filters` / `traverse` / `output`), translates it into an Eloquent query, and returns results as JSON. The controller method `QueryController::execute()` does not enforce an authorization gate, unlike `store()` and `massDestroy()` in the same controller which are correctly protected. As a result, any authenticated account — including the read-only Auditor role — can query models beyond its intended scope, including the `User` model. Additionally, the `password` column, although declared `$hidden`, is not excluded from filter predicates, which allows it to be used in `LIKE` conditions. The `schema()` and `schemaModel()` endpoints of the same controller are similarly unguarded. The Query Engine is read-only; integrity and availability are not affected. Version 2025.05.19 patches the issue.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
sourcentis · mercatorpublic PoCs found — 1
githubgithub.com/hadhub/CVE-2026-49344-Mercator-JSON-DSL★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.