Home / Help centre / Results & findings
Results & findings
My finding shows a file path and line number instead of a URL. Is something wrong?
Nothing is wrong. White-box scans read your code, so their findings show the source file and line range as the Location, and add an Endpoint line when the issue maps to a route. Black-box findings have no code, so they show an HTTP method and URL.
Why this happens
Location depends on the scan type. A black-box scan only sees the running app, so its findings point to a request, such as a method and a path. A white-box scan also reads the repository. It can name the exact place in your code that causes the issue.
That is the point of white-box testing. A developer gets a file and a line, not just a URL to guess from.
| Scan type | Location shows | Example |
|---|---|---|
| White-box | Source file and line range, plus an Endpoint line | apps/api/src/routes/example.ts:349 |
| Black-box | HTTP method and path or URL | POST /search |
How to fix it
- Open Issues or the Findings tab on the scan and click the row.
- On the Summary tab, read Location. This is the file and line range.
- Look for the Endpoint: line. It shows the route the issue affects, for example a method and path.
- Open the Sitemap tab and filter by that path to see the note the scan wrote for the endpoint.
- Give the file and line to the developer who owns that code.
Still not working?
If a white-box finding has no endpoint, it may live in configuration or in shared code rather than in one route. For a black-box target, a finding with no code is normal.
Read how to find the endpoint for a code finding and white-box vs black-box for more. The glossary entry on white-box testing explains the idea.
Related questions
- How do I find which endpoint a white-box code finding affects?
- Why doesn't my black-box scan report code-level findings with file and line?
- What's the difference between a white-box and a black-box target?
- How do I see the full details of a finding?
- How do I see which endpoints a scan discovered?
How to read a finding in Cyberlop: Summary and Evidence
Step-by-step, with annotated screenshots.
Updated · Back to the help centre
Still stuck?
Tell us what you see on screen and an engineer will help you sort it out.