T09 · Insecure Skill Coding Practices
- Location
scripts/render_email.py:104- Finding
Unescaped Repository and AI Content Injected into HTML Email
- Content
View full analysis
{icon} #{i+1} {name} {stat['commits']} 次 ``` ```python for c in stat.get("commit_details", []): time_str = _fmt_time(c.get("time", "")) msg = c.get("message", "") files_html = "" for f in c.get("files", []): fname = f.get("filename", "") fdel = f.get("deletions", 0) files_html += f"""📁 {fname} -{fdel}""" commit_items += f"""""" ``` ```python if risk_notes.strip(): risk_lines = "".join( f'🕐 {time_str}{msg}{files_html}{line}\n' for line in risk_notes.strip().splitlines() if line.strip() ) ``` ```python现状:{ai_overview}
下一步建议:{ai_suggestion}
``` ### Technical Analysis Repository names, usernames, branch names, commit messages, filenames, inactive-member fields, and AI-generated text are inserted directly into HTML using formatted strings. No HTML escaping or sanitization occurs before interpolation. Several of these values are controllable by repository contributors. A contributor can create a commit message, branch, or filename containing HTML such as an external image, dec ...[truncated 1511 chars]- Remediation
