Nextcloud Tables vulnerabilities

In Nextcloud Tables (versions 0.9.0 to 0.9.7 and 1.0.0 to 1.0.2), missing sanitization allows a user with access to perform a limited SQL injection in the ORDER BY clause, enabling extraction of a single bit per request or database delay.

Nextcloud Tables from version 0.8.0 to before 1.0.4 exposes view filter criteria to users with read-only permissions. This issue is patched in versions 1.0.4 and 2.0.0.

Nextcloud Tables (versions prior to 0.8.7 and 0.9.4) allows authenticated users to view metadata of columns in other tables of the Tables app by modifying the numeric ID in a request. This vulnerability is fixed in 0.8.7 and 0.9.4.

Nextcloud Tables before versions 0.8.6 and 0.9.3 allows a malicious user to create their own table and then move a column to a victim's table. This vulnerability is fixed in versions 0.8.6 and 0.9.3.

Nextcloud Tables prior to 0.8.9, 0.9.6, and 1.0.1 did not limit the information about which table (numeric ID) is shared with which groups or users and the respective permissions to privileged users. This vulnerability is fixed in 0.8.9, 0.9.6, and 1.0.1.

Nextcloud Tables allows you to create your own tables with individual columns. Prior to 0.7.6, 0.8.8, and 0.9.5, when importing a table, a user was able to specify files on the server and when their format is supported by the used PhpSpreadsheet library they would be included and their content leaked to the user.