Skip to content

[SEC] restrict CORS to authorized extension IDs and integrate with settings#2

Open
RaoufGhrissi wants to merge 1 commit intomasterfrom
master-configure-cors
Open

[SEC] restrict CORS to authorized extension IDs and integrate with settings#2
RaoufGhrissi wants to merge 1 commit intomasterfrom
master-configure-cors

Conversation

@RaoufGhrissi
Copy link
Copy Markdown

@RaoufGhrissi RaoufGhrissi commented Apr 14, 2026

Fixes a security issue where any Firefox extension could access the server without restriction. Granular control is now provided via a dedicated CORS configuration modal.

Also removes legacy 'cors_origins' from the main settings store and deletes the obsolete 'ServerSettings.vue', as CORS configuration is now managed through a dedicated model and storage namespace.

@RaoufGhrissi RaoufGhrissi changed the title [SEC] restrict CORS to authorized extension IDs and integrate with se… [SEC] restrict CORS to authorized extension IDs and integrate with settings Apr 15, 2026
…ttings

Fixes a security issue where any Firefox extension could access the server without restriction.
Granular control is now provided via a dedicated CORS configuration modal.

Also removes legacy 'cors_origins' from the main settings store and deletes the obsolete 'ServerSettings.vue', as CORS configuration is now managed through a dedicated model and storage namespace.
@RaoufGhrissi RaoufGhrissi force-pushed the master-configure-cors branch from 3ddcc1a to dcc339a Compare April 15, 2026 14:47
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