CVE-2026-6356
Privilege Escalation via Parameter Manipulation in Web Application
Publication date: 2026-04-22
Last updated on: 2026-04-22
Assigner: CERT/CC
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| augmentt | web_application | to 2025-10-01 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1220 | The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a privilege escalation flaw in the Augmentt web application. It allows a standard user to increase their privileges to those of a super administrator by manipulating HTTP request parameters.
Specifically, after logging in as a standard user and navigating to the "Support" menu under "Management," an attacker can intercept the HTTP response using a proxy tool, modify the permission parameter, and forward the altered response to gain unauthorized access to administrative functions.
This unauthorized access enables the attacker to view and modify sensitive administrative data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows standard users to escalate their privileges to super administrator level, enabling unauthorized access and modification of sensitive administrative data.
Such unauthorized access and potential modification of sensitive information can lead to violations of common standards and regulations like GDPR and HIPAA, which require strict controls over access to personal and sensitive data.
Failure to prevent privilege escalation and unauthorized data access may result in non-compliance with these regulations, exposing the organization to legal and financial penalties.
How can this vulnerability impact me? :
The vulnerability can have serious impacts by allowing unauthorized users to gain super administrator privileges.
- Unauthorized access to sensitive administrative data.
- Modification of critical information that should only be accessible to administrators.
- Potential compromise of the integrity and confidentiality of the system.
- Increased risk of further exploitation or malicious activities within the affected application.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring and analyzing HTTP requests and responses for unauthorized parameter manipulation attempts. Specifically, intercepting HTTP traffic to the Augmentt web application and inspecting the parameters related to user permissions can reveal attempts to escalate privileges.
Using a proxy tool such as Burp Suite or OWASP ZAP, you can capture and modify HTTP requests and responses to check if the permission parameter can be altered to gain super administrator access.
Commands or tools to assist detection include:
- Using curl or wget to send HTTP requests and observe responses for permission parameters.
- Using proxy tools (e.g., Burp Suite) to intercept and modify HTTP requests/responses.
- Network traffic capture tools like tcpdump or Wireshark to monitor HTTP traffic to the web application.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include enforcing server-side role and permission checks to ensure that user roles are retrieved securely from the backend database rather than relying on client-side controls.
Additionally, all API endpoints related to sensitive menu items must implement mandatory access control checks independently of the client interface to prevent unauthorized data processing.
It is also recommended to monitor and restrict the ability to manipulate HTTP request parameters and to apply patches or updates from the vendor once available.