Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
5DescriptionCVE.org
A vulnerability in the web application allows standard users to escalate their privileges to those of a super administrator through parameter manipulation, enabling them to access and modify sensitive information.
AnalysisAI
Privilege escalation in Augmentt 1.0 allows authenticated low-privilege users to manipulate HTTP parameters and gain super administrator access, exposing all tenant data and configurations to unauthorized modification. CVSS 9.6 critical severity with scope change indicates cross-tenant impact potential. Public proof-of-concept code exists on GitHub (PENGUINSECQ repository). SSVC framework rates this as proof-of-concept exploitation with partial technical impact, not automatable due to authentication requirement.
Technical ContextAI
This is an Insecure Direct Object Reference (IDOR) or parameter tampering vulnerability (CWE-1220: Insufficient Granularity of Data Element) in Augmentt's web application. CWE-1220 indicates the application uses overly broad privilege levels without properly validating parameter values that control access scope. The vulnerability exists in web API endpoints or form handlers where user-supplied parameters (likely user ID, role ID, or tenant ID values) are trusted without server-side authorization checks. The CVSS scope change (S:C) suggests the privilege escalation crosses trust boundaries, potentially allowing access to other organizational tenants in a multi-tenant SaaS architecture. Augmentt is an IT management and documentation platform used by managed service providers (MSPs), making cross-tenant access particularly severe as it could expose multiple client organizations.
RemediationAI
Upgrade to a patched version of Augmentt if released by the vendor-check https://nvd.nist.gov/vuln/detail/CVE-2026-6356 and contact Augmentt support for current patch status as no specific fix version is confirmed in available data. Until patching, implement compensating controls: enforce strict role-based access control (RBAC) validation on the server side for all API endpoints and form submissions, implement parameter integrity checks using HMAC signatures or encrypted tokens for role/privilege identifiers to prevent client-side manipulation, deploy web application firewall (WAF) rules to detect and block requests with suspicious parameter patterns (e.g., role escalation attempts in JSON/XML payloads), enable comprehensive audit logging for all privilege changes and administrative actions to detect exploitation attempts, and segment user accounts by tenant with database-level row security policies to limit cross-tenant exposure if privilege escalation occurs. These controls add latency to request processing and require application architecture changes, but are necessary to prevent exploitation in the absence of a vendor patch.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-24750
GHSA-pmj4-wrc3-26hm