#034Guide4 min
Assess the real impact of a vulnerability
Separate the observed weakness from possible losses, then decide what to contain and verify.
Hackaiz team · updated 21/11/2026

01Begin with what was actually observed
A vulnerability’s real impact is the consequence it can have in your application, not just the severity word attached to it. In Projects, open the project and the relevant finding. Read What was found, Evidence and Why does it matter? together. Record the resource involved, the analyzed version and the permissions needed to reach it. Those details distinguish an exposed customer-data route from a similar code pattern used only in a test fixture.
The detail page can present Scenario, Possible loss, Speed, Is this happening already? and Do now. Use these explanations to structure your investigation, not as a forensic conclusion. A demonstration that a route is accessible is not evidence that an attacker has already used it. Likewise, a description of possible losses is not a measured financial loss or a count of affected customers. Confirm operational facts with the people responsible for the application and its records.
02Trace access through to a concrete consequence
Ask three questions: who can trigger the weakness, what can they reach, and what can they do there? For example, a route that returns another user’s invoice could expose personal or commercial information. A route that also permits changes creates a different risk to data integrity. The report must support the behavior you describe; do not turn an observed read into a claim that deletion or administrative takeover is possible without additional evidence.
For a secret, distinguish a credential intended to be public from a privileged service key. If a privileged credential has been exposed, removing its text from the repository does not invalidate copies already taken. The finding page explains that revocation belongs with the provider; Hackaiz cannot revoke that third-party access for you. Assess the credential’s actual permissions and replace it safely. Do not test its powers by accessing unrelated data or carrying out destructive operations.
03Combine severity, confidence and deployment context
Danger, To fix and To watch summarize severity, while the confidence label expresses the strength of the finding. A serious possible consequence with limited proof calls for careful confirmation; a strongly evidenced weakness on a live privileged path may demand immediate containment. Avoid treating either the label or confidence as a substitute for identifying the affected data and service. A defect in code can warrant correction even when you have not established that it is deployed.
For a website or API, Hackaiz requires proof of domain control before analysis. You can provide the DNS TXT record _hackaiz, the HTTPS file /.well-known/hackaiz-verification.txt, or ask the project’s AI to create that file. Domain proof authorizes the target analysis; it does not tell you what the exposed data means to the business. Keep that authorization boundary intact when gathering more evidence.
- 1Name the affected resource and the user or anonymous access involved.
- 2Separate the observed behavior from consequences that remain hypothetical.
- 3Ask the application owner which real data and business processes use that resource.
- 4Choose a containment measure and a verification condition that match the demonstrated behavior.
04Contain the risk without overstating certainty
Write a short decision note in your own records: observed behavior, possible consequence, evidence limits and next action. For an exposed privileged secret, revocation may be needed before a code cleanup is complete. For an access-control issue, a targeted restriction may be appropriate while a durable change is reviewed. Test that restriction against legitimate use rather than disabling broad parts of the application without understanding the effect.
When a GitHub fix is available, it is a draft pull request that requires human review and approval; Hackaiz never merges it automatically. After deployment, repeat the relevant verification before calling the weakness resolved. Further analysis uses credits, and unticked checks are neither run nor billed. Tell stakeholders exactly what was verified. A confirmed weakness justifies corrective action, but it does not by itself prove a past compromise or provide a guarantee about every other application path.
Frequently asked questions
Take the next step
Was this article helpful?