Investigate Hardcoded HTTP Basic-auth credentials
Build 0.649 · Scan 2026-10-07T07:23:59.794Z
1 distinct recorded findings; 1 have inspectable metadata. Locations are representative, not an inventory of every source match.
Hardcoded HTTP Basic-auth credentials (a username:password pair, base64-encoded in an Authorization header) are embedded in the app. If the endpoint is live, anyone can extract and reuse them — rotate the credential and move auth server-side. Confirm it isn't a placeholder.
Static evidence does not establish runtime impact. Source excerpts and line numbers were not recorded.
Evidence preview
- Evidence type
- Static string match
- Representative location
assets/www/scripts/IWE.MainFlow.NewOrderCharity.mvc.js- Recorded match
Pattern recorded; identifying value redacted.- Detector rule
basic_auth_header- Recorded file locations
assets/www/scripts/IWE.MainFlow.NewOrderCharity.mvc.jsassets/www/scripts/IWE.Common.Login.mvc.jsassets/www/scripts/IWE.Common.CreateAccount.mvc.jsassets/www/scripts/IWE.controller.jsassets/www/scripts/IWE.MainFlow.NewOrderWithUber.mvc.jsassets/www/scripts/IWE.MainFlow.NewLocations.mvc.jsassets/www/scripts/IWE.Common.CreateAccountOld.mvc.jsassets/www/scripts/IWEDB.model.jsassets/www/scripts/IWE.Common.CreateAccountOTP.mvc.jsassets/www/scripts/IWE.MainFlow.CompleteRegistration.mvc.js