HAX CMS Backend Lacks Comprehensive Authorization Checks
haxtheweb issues
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @haxtheweb/haxcms-nodejs npm |
|
|
| elmsln/haxcms Packagist |
|
|
haxtheweb issues
| Product | Affected | Fixed in |
|---|---|---|
| @haxtheweb/haxcms-nodejs npm |
|
|
| elmsln/haxcms Packagist |
|
|
HAX CMS allows you to manage your microsite universe with PHP or NodeJs backends. In versions 11.0.13 and below of haxcms-nodejs and versions 11.0.8 and below of haxcms-php, API endpoints do not perform authorization checks when interacting with a resource. Both the JS and PHP versions of the CMS do not verify that a user has permission to interact with a resource before performing a given operation. The API endpoints within the HAX CMS application check if a user is authenticated, but don't check for authorization before performing an operation. This is fixed in versions 11.0.14 of haxcms-nodejs and 11.0.9 of haxcms-php.
From the CVE record · GitHub_M
HAX CMS API endpoints check whether a user is authenticated but do not check whether that user is authorized to interact with a resource. An authenticated user can therefore perform operations on resources without the required permission. The issue affects the Node.js and PHP backends.
Teams running @haxtheweb/haxcms-nodejs or elmsln/haxcms before 11.0.14 should check their installations; the description also identifies haxcms-php through 11.0.8 as affected.