Potential fix for code scanning alert no. 6: Stored cross-site scripting

[NelsonBN]

Potential fix for https://github.com/craft-code-club/blog-c3/security/code-scanning/6

To fix the stored cross-site scripting vulnerability, we need to sanitize the post.id value before using it in the href attribute of the Link component. The best way to achieve this is by using a library that provides HTML escaping functionality to ensure that any potentially harmful characters are properly encoded.

We will use the escape-html library to escape the post.id value before using it in the Link component. This will prevent any malicious scripts from being executed.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

[cloudflare-workers-and-pages]

Deploying blog-c3 with    Cloudflare Pages

Latest commit:	babd8ec
Status:	🚫  Build failed.

View logs

[github-actions]

🚀 Preview Url 🚀

https://aafffc5d.blog-c3.pages.dev

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

Files not reviewed (1)

• package.json: Language not supported

Comments suppressed due to low confidence (2)

src/app/topics/[topic]/page.tsx:74

• Ensure that post.id is a string before passing it to escapeHtml to prevent unexpected behavior if post.id is not a string.

<Link href={`/posts/${escapeHtml(post.id)}`}>

src/app/topics/[topic]/page.tsx:74

• Ensure that post.id is a string before passing it to escapeHtml to prevent unexpected behavior if post.id is not a string.

<Link href={`/posts/${escapeHtml(post.id)}`}>