It is possible to perform actions in the application and make it look as if they were performed by the system or another user. Examples include sending messages that appear to come from the system and modifying data in the name of other users (who may have more privileges).
Impersonate the application to increase the chances of a successful phishing or social engineering attack.
Avoid the usage of custom system messages that can be tampered by an user.
Authenticated attacker from the Internet.
Expected Remediation Time
Default score using CVSS 3.1. It may change depending on the context of the src.
- Attack vector: N
- Attack complexity: L
- Privileges required: L
- User interaction: N
- Scope: U
- Confidentiality: N
- Integrity: L
- Availability: N
- Exploit code madurity: X
- Remediation level: U
- Report confidence: C
- Vector string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N/E:X/RL:U/RC:C
- Base: 4.3
- Temporal: 4.3
- Base: Medium
- Temporal: Medium
- 035.Manage privilege modifications
- 096.Set user's required privileges
- 173.Discard unsafe inputs
- 176.Restrict system objects
- 265.Restrict access to critical processes
- 320.Avoid client-side control enforcement
Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.