01 / EXECUTIVE SUMMARY
This section provides a concise overview of the injection finding, affected functionality and potential security impact.
Final content will document the exact injection condition and affected application behavior using sanitized technical details.
02 / TECHNICAL DETAILS
This section will document the affected input, application behavior and technical conditions that allowed database queries to be influenced.
The final version can include sanitized request parameters, relevant responses and an explanation of why the input was interpreted unsafely.
03 / REPRODUCTION
Reproduction steps will be documented in a predictable sequence so the issue can be verified independently.
Identify the affected input. Document the parameter or application functionality being tested.
Establish normal behavior. Capture the expected response before modifying the input.
Test the injection condition. Document the sanitized input used to demonstrate the vulnerability.
Verify the result. Record the observable response demonstrating that application behavior changed.
04 / IMPACT
The final report will describe the actual demonstrated impact and separate confirmed behavior from theoretical escalation possibilities.
This keeps the report focused on evidence instead of overstating the severity of the finding.
05 / EVIDENCE
Sanitized requests, responses, screenshots or other supporting artifacts can be inserted in this section.
Sanitized technical evidence will be inserted here during the content phase.
06 / REMEDIATION
The final remediation section will describe how the application should prevent untrusted input from altering database query structure.
Recommendations can include parameterized queries, appropriate validation and limiting database privileges where relevant to the final finding.
07 / REFERENCES
Relevant OWASP documentation and supporting technical references can be listed here.