Home / Help centre / Results & findings
Results & findings
How do I find which endpoint a white-box code finding affects?
Open the finding from a white-box scan. The Summary tab shows the code location as a file and line range, plus an Endpoint line such as DELETE with a route. To see that endpoint in context, search for it on the scan's Sitemap tab.
White-box findings point to code. Many also name the route that code serves, so you can link the two.
Steps
- Open the finding by clicking its row.
- On the Summary tab, read Location. It shows a source file and line range.
- Read the Endpoint line right below. It gives a method and route.
- Go to the scan's Sitemap tab and type the route into Filter by URL or method.
Good to know
The two lines answer different questions.
| Line | Answers |
|---|---|
| Location | Where in the code is the weak spot? |
| Endpoint | Which route does a request use to reach it? |
The sitemap row for that route shows the parameters and a note from the scan, and sometimes a role chip. Together with the finding's Evidence tab, you get both ends: the file to change and the request that reaches it.
Not every white-box finding names an endpoint. A weak setting in a config file, for example, may apply to the whole app. In that case the list shows a file and line only, or several files.
The sitemap is built in the recon phase, which maps the running app. White-box findings come from code analysis, and the Endpoint line is how the two views meet. See how to read a finding for each field.
If an endpoint is missing from the sitemap, the scan may not have reached it. Ask for help at /contact.
This link between code and route is what lets a developer move from a report to a fix without guessing, because the file shows where to change the code and the route shows how to test the change. Follow the trail. Fix the cause.
Related questions
- How do I see which endpoints a scan discovered?
- How do I filter the sitemap by URL or method?
- How do I see the full details of a finding?
- My finding shows a file path and line number instead of a URL. Is something wrong?
- Why do I see several separate findings in the same file?
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.