Skip to content

LOXS fails to detect parameters inside URL fragments #110

@bytes-Knight

Description

@bytes-Knight

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 reports Total found: 0 and Total 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

  1. Run LOXS with a URL containing query parameters in the fragment (#).
  2. Observe that no parameters are detected or tested.
Image

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

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions