Home / Help centre / Troubleshooting
Troubleshooting
I fixed the code, but the finding is still open. Why?
A finding closes when a later scan no longer detects it, or when you set its disposition to Fixed yourself. Scans read the code in the target’s repository at launch, so push your fix to that branch first. Then run a new scan and check the Diff tab.
Why this happens
Issues persist per target across scans. Cyberlop marks one Fixed only when a later scan genuinely did not re-detect it. Until then it stays open. For that to happen, a new scan has to run, and it has to read the code you fixed, which means the fix must sit in the branch the target uses.
How to fix it
- Make sure the change is in the repository and branch set on the target. Scans clone the latest code at launch.
- Click Scan on the profile or on Recent Scans.
- On the new scan, Diff lists New, Fixed and Regressed findings against the previous completed scan.
- If it is still present, open it and compare the location with your change. The fix may not cover that path.
- Choose Fixed under Disposition and click Update status.
Mark a finding Fixed by hand only when you are sure. If the issue comes back in a later scan, Cyberlop flags it as a Regression instead of a new finding. A re-scan is the better proof, since it tests the live app again and shows whether the old flaw still answers.
Still not working?
Check these common causes. The fix is on another branch than the target’s. The staging site still runs old code. A failed scan stopped before it reached that area. A failed scan can still hold findings, but it may not retest everything. The guide to confirming fixes and wrong branch article cover each. Need help? Use the contact page.
Related questions
- How do I confirm my fixes worked?
- How do I mark a finding as fixed?
- Why was a finding marked Fixed when I didn't change it?
- Why did a finding I fixed come back as a Regression?
- Does Cyberlop scan the latest code from my repository each time?
How to verify a vulnerability fix with fixed and regressed issues
Step-by-step, with annotated screenshots.
Updated · Back to the help centre
Error still showing?
Send us the exact message and the page you were on. We will reply with the fix.