fix: database operations in security/security_log in security_log.v

[orbisai0security]

Summary

Fix critical severity security issue in security/security_log.v.

Vulnerability

Field	Value
ID	V-002
Severity	CRITICAL
Scanner	multi_agent_ai
Rule	V-002
File	security/security_log.v:36

Description: Database operations in security/security_log.v and issue.v use variables (user_id, issue_id, repo_id) directly in query construction without confirmed use of parameterized queries or ORM-level escaping. If these variables are derived from HTTP request parameters and interpolated into raw query strings, an attacker can inject malicious SQL to read, modify, or delete records across the SecurityLog and Issue tables. The V language ORM supports parameterized queries; if raw string construction is used instead, injection is confirmed.

Changes

• security/security_log.v

Verification

• Build passes
• Scanner re-scan confirms fix
• LLM code review passed

---

Automated security fix by OrbisAI Security