Skip to content

fix(security): 2 improvements across 2 files#2560

Closed
tomaioo wants to merge 2 commits into
TurboWarp:masterfrom
tomaioo:fix/security/unsafe-url-construction-in-profanityapi-
Closed

fix(security): 2 improvements across 2 files#2560
tomaioo wants to merge 2 commits into
TurboWarp:masterfrom
tomaioo:fix/security/unsafe-url-construction-in-profanityapi-

Conversation

@tomaioo

@tomaioo tomaioo commented Jul 4, 2026

Copy link
Copy Markdown

Summary

fix(security): 2 improvements across 2 files

Problem

Severity: Medium | File: extensions/TheShovel/profanityAPI.js:L33

The profanityAPI extension constructs a URL by directly concatenating user-controlled input (TEXT) into a URL without URL encoding. This could lead to URL injection attacks, allowing manipulation of the request parameters sent to purgomalum.com. While the impact is limited to the external API, it could cause unexpected behavior or API abuse.

Solution

Use URL encoding for the text parameter, e.g., encodeURIComponent(TEXT) when constructing the URL.

Changes

  • extensions/TheShovel/profanityAPI.js (modified)
  • extensions/fetch.js (modified)

tomaioo added 2 commits July 4, 2026 11:06
- Security: Unsafe URL construction in profanityAPI extension
- Security: Unvalidated user input in fetch extension

Signed-off-by: tomaioo <203048277+tomaioo@users.noreply.github.com>
- Security: Unsafe URL construction in profanityAPI extension
- Security: Unvalidated user input in fetch extension

Signed-off-by: tomaioo <203048277+tomaioo@users.noreply.github.com>
@github-actions github-actions Bot added the pr: change existing extension Pull requests that change an existing extension label Jul 4, 2026
@GarboMuffin

Copy link
Copy Markdown
Member

Hallucinated slop is not welcome here.

@GarboMuffin GarboMuffin closed this Jul 4, 2026
@GarboMuffin GarboMuffin added the invalid This doesn't seem right label Jul 4, 2026
@Brackets-Coder

Copy link
Copy Markdown
Contributor

Good to know

@GarboMuffin

GarboMuffin commented Jul 4, 2026

Copy link
Copy Markdown
Member

To be clear, I do run LLM security checks on a lot of things in here. We've found and fixed things that way. But neither of these are even remotely real issues, and it's clear that no human even looked at it before you created this.

The profanity extension is not listed on our website and probably not used by anyone. The "vulnerability" you report is that the project can put arbitrary text at the URL. That's nonsense. The project can also just use the fetch extension to do the same thing. Is it a bug to not be escaping there? Maybe. But it's a niche bug in an extension nobody uses so whatever.

Your proposed change to the fetch extension is comical. Scratch.fetch already does these checks for you. And your proposed change breaks relative path fetches as used by some packaged projects.

@GarboMuffin

Copy link
Copy Markdown
Member

PR author was blocked for 7 days.

@GarboMuffin

Copy link
Copy Markdown
Member

Changing block to permanent because PR author's whole deal is sending slop out to random github repos.

@Brackets-Coder

Copy link
Copy Markdown
Contributor

Good to know

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

Labels

invalid This doesn't seem right pr: change existing extension Pull requests that change an existing extension

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants