Skip to content

🛡️ Sentinel: Fix XSS in blog route and harden JSON-LD metadata - #67

Open
Simonc44 wants to merge 1 commit into
mainfrom
sentinel-fix-blog-xss-13161617624071314981
Open

🛡️ Sentinel: Fix XSS in blog route and harden JSON-LD metadata#67
Simonc44 wants to merge 1 commit into
mainfrom
sentinel-fix-blog-xss-13161617624071314981

Conversation

@Simonc44

@Simonc44 Simonc44 commented Jul 5, 2026

Copy link
Copy Markdown
Owner

🚨 Severity: HIGH
💡 Vulnerability: Cross-Site Scripting (XSS) in the blog route.
🎯 Impact: Malicious users could inject arbitrary HTML/JS if they could control the blog post content (e.g. through a compromised data source or if the feature were expanded to user-submitted content). Also, JSON-LD metadata was not properly escaped, posing a risk of script injection in the <head>.
🔧 Fix:

  1. Added a robust escapeHTML utility.
  2. Updated the renderContent function in blog.$slug.tsx to follow an "escape first, then transform" pattern.
  3. Implemented a javascript: protocol check for markdown-style links.
  4. Used the safeJsonLd utility (previously internal to __root.tsx) for all JSON-LD metadata blocks.
    ✅ Verification: Ran pnpm build and verified the blog route visually using Playwright. Checked that formatting (bold, links) still works correctly while raw HTML is safely escaped.

PR created automatically by Jules for task 13161617624071314981 started by @Simonc44

- Implemented safe HTML escaping in the custom markdown-lite renderer for blog posts.
- Added a shared `escapeHTML` utility in `src/lib/api.ts`.
- Exported `safeJsonLd` and added `createArticleSchema` to safely handle JSON-LD metadata in routes.
- Sanitized URLs in blog content to prevent `javascript:` protocol injection.
- Added a security learning entry in `.jules/sentinel.md`.

Co-authored-by: Simonc44 <216070312+Simonc44@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel

vercel Bot commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
mandat Ready Ready Preview, Comment Jul 5, 2026 4:09am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant