Skip to content

🔒 [security fix] Resolve DOM-based XSS in post titles and enable markdown sanitization#2

Open
OscarPastry wants to merge 1 commit into
mainfrom
fix-xss-dangerouslysetinnerhtml-7165684055319761716
Open

🔒 [security fix] Resolve DOM-based XSS in post titles and enable markdown sanitization#2
OscarPastry wants to merge 1 commit into
mainfrom
fix-xss-dangerouslysetinnerhtml-7165684055319761716

Conversation

@OscarPastry
Copy link
Copy Markdown
Owner

This PR addresses a DOM-based XSS vulnerability where post titles were rendered using dangerouslySetInnerHTML with unsanitized data. It also proactively enables HTML sanitization for the markdown content processing to ensure overall site security.

🎯 What:

  • Fixed DOM-Based XSS via dangerouslySetInnerHTML in app/secret-editor/page.js, app/posts/[slug]/page.js, app/components/HamburgerMenu.js, and app/page.js.
  • Enabled sanitization for Markdown-to-HTML conversion in lib/posts.js.
  • Restored package-lock.json.

⚠️ Risk:

Using dangerouslySetInnerHTML with unsanitized user input (post titles) bypasses React's built-in XSS protection, allowing malicious scripts to be executed in the context of users' browsers. Similarly, unsanitized Markdown content could lead to XSS if malicious HTML is included.

🛡️ Solution:

  • Replaced dangerouslySetInnerHTML with standard JSX interpolation ({post.title}), which automatically escapes content.
  • Configured remark-html to use sanitize: true when processing post content.

PR created automatically by Jules for task 7165684055319761716 started by @OscarPastry

…ization

- Replace `dangerouslySetInnerHTML` with safe React interpolation for post titles in multiple components.
- Enable `sanitize: true` in `remark-html` to ensure markdown content is safely converted to HTML.
- Restore `package-lock.json` to maintain deterministic builds.

Co-authored-by: OscarPastry <181119116+OscarPastry@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
Copy link
Copy Markdown

vercel Bot commented Feb 27, 2026

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

Project Deployment Actions Updated (UTC)
club-blog-pt75 Building Building Preview, Comment Feb 27, 2026 3:03pm

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