Cross-user object access via user-controlled key
Published Jun 26, 2026 · Updated Jun 26, 2026
Authorization bypass in Majestic Support 1.1.7 and earlier allows remote authenticated users to access objects beyond their authorization. Patchstack identifies an insecure direct object reference but does not disclose the affected object, handler, identifier parameter, or missing ownership check. Subscriber access is sufficient; the published impact is limited to unauthorized data reading or modification, with no service interruption.
Summary
What happened
Authorization bypass in Majestic Support 1.1.7 and earlier allows remote authenticated users to access objects beyond their authorization. Patchstack identifies an insecure direct object reference but does not disclose the affected object, handler, identifier parameter, or missing ownership check. Subscriber access is sufficient; the published impact is limited to unauthorized data reading or modification, with no service interruption.
The record
- CVE
- CVE-2026-57646
- Published
- Jun 26, 2026
- Updated
- Jun 26, 2026
- Vendor
- Majestic Support
- Product
- Majestic Support
- Classifications
- CWE-639, CAPEC-180, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2026CVE publishedPublication date reported by the CVE source.
- Jun 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=1.1.7 changes=[{"at":"1.1.8","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo