Skip to content

fix: Fix the storage of sanitized project name - EXO-86231#600

Merged
azayati merged 1 commit into
developfrom
merge-86231
May 11, 2026
Merged

fix: Fix the storage of sanitized project name - EXO-86231#600
azayati merged 1 commit into
developfrom
merge-86231

Conversation

@azayati
Copy link
Copy Markdown
Member

@azayati azayati commented May 11, 2026

Prior to this change, when creating or editing a task project, a JavaScript payload inserted in the name field could be executed when the task project is deleted, leading to an XSS vulnerability, this is already fixed with a previous commit by storing a sanitized project name which is not coherent with the architectural choice made is: Sanitize OnRead from DB and not altering data OnWrite on DB. After this commit, we ensure to sanitize the project name only when getting projects and not when storing them.

Resolves Meeds-io/si#11

Prior to this change, when creating or editing a task project, a
JavaScript payload inserted in the name field could be executed when the
task project is deleted, leading to an XSS vulnerability, this is
already fixed with a previous commit by storing a sanitized project name
which is not coherent with the architectural choice made is: Sanitize
OnRead from DB and not altering data OnWrite on DB. After this commit,
we ensure to sanitize the project name only when getting projects and
not when storing them.

Resolves Meeds-io/si#11
@azayati azayati changed the title fix: Fix the storage of sanitized project name - EXO-86231 (#599) fix: Fix the storage of sanitized project name - EXO-86231 May 11, 2026
@azayati azayati requested a review from Jihed525 May 11, 2026 08:55
@sonarqubecloud
Copy link
Copy Markdown

@azayati azayati enabled auto-merge (squash) May 11, 2026 08:58
@azayati azayati merged commit 4e2769b into develop May 11, 2026
11 checks passed
@azayati azayati deleted the merge-86231 branch May 11, 2026 09:00
exo-swf pushed a commit that referenced this pull request May 11, 2026
Prior to this change, when creating or editing a task project, a
JavaScript payload inserted in the name field could be executed when the
task project is deleted, leading to an XSS vulnerability, this is
already fixed with a previous commit by storing a sanitized project name
which is not coherent with the architectural choice made is: Sanitize
OnRead from DB and not altering data OnWrite on DB. After this commit,
we ensure to sanitize the project name only when getting projects and
not when storing them.

Resolves Meeds-io/si#11
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.

2 participants