-
Notifications
You must be signed in to change notification settings - Fork 290
Closed
Description
Summary
LOXS works correctly with standard query parameters (e.g., ?q=
) but fails to detect and scan parameters when they are present inside the fragment portion of a URL (e.g., #q=
).
Example
- ✅ Works:
https://www.amsoilindustrial.com/search/?q=xss&t=totalProductsTab
- ❌ Fails:
https://www.amsoilindustrial.com/search/#q=xss&t=totalProductsTab
Observed Behavior
- When scanning with
?q=
, LOXS identifies and processes the parameter as expected. - When scanning with
#q=
, LOXS reportsTotal found: 0
andTotal scanned: 0
even though parameters are present.
Expected Behavior
LOXS should also parse and test parameters that appear in the fragment portion of URLs (#
), as many modern applications pass data through hash fragments (e.g., single-page apps).
Steps to Reproduce
- Run LOXS with a URL containing query parameters in the fragment (
#
). - Observe that no parameters are detected or tested.

This limits LOXS’s coverage on modern web applications that use fragment-based routing or client-side parameters, potentially missing XSS vectors.
Metadata
Metadata
Assignees
Labels
No labels