Findings
All security vulnerabilities across your projects
The user profile bio field does not properly sanitize HTML input, allowing stored cross-site scripting attacks. Malicious JavaScript can be injected that executes when other users view the profile.
The `/api/search` endpoint is vulnerable to SQL injection through the `q` parameter. An attacker can extract sensitive data from the database by injecting SQL queries through the search functionality. The parameter is directly concatenated into the SQL query without parameterization or sanitization.
The `tamkeen-prod-reports` S3 bucket has a public ACL allowing anyone on the internet to list and read all objects, including sensitive financial reports and PII data.
Password reset tokens are not invalidated after use. An attacker who intercepts a reset token can reuse it multiple times to change the password, even after the legitimate user has already reset their password.
The `/api/transactions/:id` endpoint does not verify that the authenticated user owns the requested transaction. Any authenticated user can view other users' transaction details by iterating through transaction IDs.
The login endpoint does not implement rate limiting, allowing unlimited authentication attempts. This enables brute-force and credential-stuffing attacks against user accounts.
Several state-changing POST endpoints do not validate CSRF tokens, allowing an attacker to craft malicious pages that perform actions on behalf of authenticated users.
The webhook configuration endpoint allows specifying arbitrary URLs. An attacker can use this to probe internal network services, read AWS metadata, or access other internal resources.

