Denis, do you have access to severity level? Is this really minor?

major ?

I don't like block …

One could argue it's blocking the workflow to assign permissions...? Or?

@ollehar : do you have any idea why this issue didn't happen before ?

See forum post :

I immediately downgraded to 4.4.1 again.

by user
… …

Public survey : no issue ;)

partial_block if you use roles only :)

https://github.com/LimeSurvey/LimeSurvey/pull/1755

I'm sure at 100% of my fix but

• Rename a function (not in API)
• Remove the call of https://manual.limesurvey.org/BeforeHasPermission with userid = 0 when checking permission for userid > 0

Renaming functions are fine. As long as it makes sense. :)

Public survey : no issue ;)

I consider "block" to be "blocking for a workflow [for many users]" - can be admin interface or anything.

Partial block = blocking workflow for some users.

I consider "block" to be "blocking for a workflow [for many users]" - can be admin interface or anything.

Here :

• before : some user didn't have access (without issue)
• after : all user have access to all (with issue)

But all action can be done ;)

It's not block (but it's a major potential leak of data ;) )

But all action can be done ;)

Not the workflow of controlling permissions...

Anyway.

:D

major potential leak of data

But on a new feature ;) role didn't exist in 3.X

New severity level for security issues needed?

Maybe :)

But i like to have
minor
major
block

for start

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=31053

Fixed in Release 4.4.7+210215