Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain low-privilege Mercator login
-
DeliveryReach /admin/queries/execute endpoint
-
ExploitSubmit JSON DSL targeting User model
-
InstallUse LIKE filters on hidden password column
-
C2Infer password hashes blindly
-
ExecuteCrack hashes offline
-
ImpactEscalate to administrative access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection PII protection
|
| Exploitation Conditions | Requires (1) a valid authenticated session on the target Mercator instance - any role suffices, including the read-only Auditor role, because the |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N) of 7.1 accurately reflects a network-reachable, low-complexity confidentiality-only flaw requiring low privileges - any authenticated account, including the explicitly read-only Auditor role, is sufficient. There is no EPSS score, KEV listing, or public POC referenced, so the signal set points to a known but not yet weaponized issue; given Mercator's niche deployment (internal IS-mapping tool typically behind SSO/VPN), real-world exposure is likely limited to insider-threat and post-foothold scenarios rather than mass scanning. The integrity/availability impact is correctly zero (the engine is read-only), but the ability to extract password hashes via |
| Exploit ScenarioDerived | An attacker with any valid Mercator login (e.g. a compromised Auditor contractor account) sends a POST to |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 19, 2026
Authorization bypass in Mercator information system mapping application prior to version 2025.05.19 allows any authenticated user - including the read-only Auditor role - to query arbitrary Eloquent models via the unprotected /admin/queries/execute endpoint. The flaw permits enumeration of the User model and even allows the supposedly $hidden password column to be probed via LIKE filter predicates, enabling blind extraction of password hashes. No public exploit identified at time of analysis, but the vendor advisory (GHSA-q3r8-3h7c-96w3) confirms the issue and ships a fix.
RemediationAI
Vendor-released patch: upgrade Mercator to version 2025.05.19 or later, which adds the missing authorization gate to QueryController::execute(), schema(), and schemaModel() (see https://github.com/sourcentis/mercator/security/advisories/GHSA-q3r8-3h7c-96w3). Where immediate upgrade is not possible, restrict access to /admin/queries/execute, /admin/queries/schema, and /admin/queries/schemaModel at the reverse proxy or web server (e.g. nginx/Apache location blocks limited to admin source IPs), accepting that this disables the Query Engine for Auditor-role users; alternatively, temporarily disable or downgrade the Auditor role and any non-administrative accounts until the patch is applied, with the trade-off of reduced audit functionality. As a precaution, rotate all Mercator user passwords after patching, since password-hash enumeration via LIKE may have occurred undetected.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Mercator is an open-source PHP/Laravel web application by Sourcentis used for mapping enterprise information systems (assets, applications, processes). Its Query Engine exposes a JSON DSL (from/select/filters/traverse/output) that QueryController::execute() translates into Eloquent ORM queries. The root cause is CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor): peer methods store() and massDestroy() enforce an authorization gate, but execute(), schema(), and schemaModel() were left unguarded, so role-based access controls are bypassed at the controller layer. Compounding this, Laravel's $hidden array only suppresses fields from serialized output - it does not prevent those columns from being referenced in WHERE/LIKE predicates, allowing boolean/inference-based extraction of the password hash column even though it is never returned directly. The affected CPE is cpe:2.3:a:sourcentis:mercator:* for all versions prior to 2025.05.19.
Know when Mercator gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Network-reachable endpoint exploitable by any authenticated user (PR:L) with no user interaction; only confidentiality is impacted (read-only Query Engine exposing User data and password hashes).
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
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.
Executive ViewAI
Mercator information system mapping application versions prior to 2025.05.19 contain an authorization bypass vulnerability allowing any authenticated user, including read-only Auditor accounts, to execute arbitrary database queries and extract sensitive data including password hashes. This privilege escalation risk enables lower-privileged roles to access data intended for administrators, creating direct exposure of user credentials and authentication systems. Organizations using affected versions must patch immediately to prevent unauthorized data disclosure and account compromise.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Server-Side Request Forgery in Mercator's CVE configuration panel allows authenticated users holding the low-privilege '
Stored XSS in Mercator prior to version 2026.02.22 allows authenticated users to execute arbitrary JavaScript in other u
EUVD-2026-38071
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB