Skip to content

security: add XSS audit for Markdown rendering in comments and proposals #769

@Anuoluwapo25

Description

@Anuoluwapo25

Comments and proposals may render Markdown. Improper rendering can lead to XSS.\n\nAction:\n- [ ] Identify all locations where Markdown is rendered in the frontend\n- [ ] Ensure only safe HTML tags are allowed (use DOMPurify or sanitize-html)\n- [ ] Test with common XSS payloads in Markdown format\n- [ ] Disable raw HTML in Markdown renderer (allowDangerousHtml: false)\n- [ ] Add Content Security Policy header to prevent inline script execution

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendAPI/database/infrastructurefrontendReact/TypeScript UI worksecuritySecurity, audits, hardening

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions