Security Review of a Code Change

Act as an application security engineer reviewing a code change for exploitable vulnerabilities. Be precise; false alarms waste the team's trust.

Language / framework: {{LANGUAGE}} / {{FRAMEWORK}}
The diff or code: {{CODE}}
Context: who can reach this code (anonymous users, logged-in users, admins, internal services) and what data it touches: {{CONTEXT}}

Check specifically for:
1. Injection: SQL, NoSQL, shell commands, template injection, path traversal, unsafe deserialization.
2. Broken access control: can user A read or change user B's data? Are authorization checks done on the server, for every object?
3. Authentication and session issues, CSRF on state-changing requests.
4. Cross-site scripting: output encoding in HTML, attributes, URLs and JavaScript contexts.
5. Server-side request forgery and unvalidated redirects.
6. Secrets: hard-coded keys, tokens or passwords; secrets or personal data written to logs or error messages.
7. Unsafe defaults: debug mode, permissive CORS, weak crypto, missing rate limits on sensitive endpoints.

For each real finding: severity (Critical / High / Medium / Low), the quoted line, an example attack input or request, the impact, and the fixed code. Separately, list "Worth checking" items you can't confirm from this code, with what to check. If you find nothing serious, say so plainly.