Last modified: 2009-08-01 16:45:29 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 12110 - Split user right "editusercssjs"
Split user right "editusercssjs"
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: css
  Show dependency treegraph
Reported: 2007-11-25 21:00 UTC by MZMcBride
Modified: 2009-08-01 16:45 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description MZMcBride 2007-11-25 21:00:40 UTC
The user right "editusercssjs" should be split into "editusercss" and "edituserjs". Javascript can be dangerous, esp. on larger wikis where there are a lot of sysops. With the right split, a higher level user (e.g., bureaucrat) could be allowed to edit .js while regular sysops could edit .css.

Also, if possible, splitting this right for the MediaWiki namespace as well would probably be a good idea, though abuse there is less likely as it usually has more eyes watching it.
Comment 1 Thomas Bleher 2007-11-27 21:13:29 UTC
CSS can contain JavaScript, at least for Internet Explorer (see So this separation does not achieve the security you want to have. Of course, splitting the rights might still be a good idea to prevent sysops from accidentally inserting vulnerable JavaScript code.
Comment 2 Shinjiman 2009-08-01 16:45:29 UTC
Fixed in r54153.

Note You need to log in before you can comment on or make changes to this bug.