#045Technical4 min
Apply a fix manually and safely
Turn a finding into a reviewed code change without confusing an edit with a verified repair.
Hackaiz team · updated 21/11/2026

01Read the finding before editing
A manual fix means that you or your developer change the application rather than asking Hackaiz to publish a proposal. Start with the affected file, the evidence, and the suggested next action in the finding. Write down what must stop working for an attacker and what must continue working for a legitimate user. For example, replacing a database query assembled from request text should remove the unsafe text assembly without preventing ordinary searches. Treat this as a focused repair, not an opportunity to rewrite the whole feature.
Keep the starting version available through your normal source-control process and work in a separate branch. This is a recommended development practice, not a promise that Hackaiz creates a recovery point for manual edits. If the evidence is incomplete, first reproduce the specific scenario in an environment you are authorized to test. Do not paste production credentials or personal records into an AI conversation to explain the problem.
02Repair the security boundary
Make the change where the decision is enforced. A browser-only check cannot replace a server authorization rule, and hiding a button does not prevent a direct API request. When a finding concerns a secret shipped to the browser, moving the displayed text is not enough: move the privileged call to the server and replace the exposed credential through its provider. These are developer actions outside Hackaiz; do not assume a code edit revokes a key that has already escaped.
Read the surrounding calls and error paths before saving. For a SQL query, use the database client’s parameter placeholders instead of joining strings. For a command built from user or model input, prefer a small set of named operations with validated arguments. Review the resulting difference line by line, including configuration and dependency changes. Unrelated edits make it harder to know which change removed the weakness and harder to reverse an accidental breakage.
03Test both the blocked and allowed cases
Run your project’s tests and add a test for the behavior described in the finding. Include a legitimate request as well as the request that should now fail. For an ownership check, verify that the owner still sees the record while another account does not. Use test accounts and harmless records under your control. A successful build only establishes that the code can be built; it does not establish that access restrictions are correct. Ask a human reviewer to inspect the security assumption as well as the syntax.
The Fixes screen separates preparation from completion. Its filters include Ready to review, Applied, and Verified; Applied · verify explicitly leaves verification outstanding. A manually edited branch is not automatically associated with a verified Hackaiz correction. If you instead use a generated proposal, Hackaiz publishes a draft GitHub pull request only after approval. A human reviews and decides whether to merge it; Hackaiz never merges it automatically.
04Check the deployed version, not just your editor
After your normal deployment, repeat the original scenario against the corrected version. Keep the tested address, the source revision, the test outcome, and the limits of the test in your own change record. A branch containing a good patch does not protect a deployment still serving the previous revision. For website or API analysis, first prove domain control using the DNS TXT record _hackaiz, the HTTPS file /.well-known/hackaiz-verification.txt, or the project AI that creates that file.
Use a new analysis as additional evidence, not as an automatic verification stamp. Hackaiz’s correction verification distinguishes replay of the original test, passing continuous-integration tests, and a match between the corrected commit and deployment. A timeout or missing deployment evidence leaves uncertainty. Analyses and correction work consume credits; leave unwanted checks unticked because they are neither run nor billed. Never describe a manual repair as complete merely because the previous warning is no longer visible.
Frequently asked questions
Take the next step
Was this article helpful?