CVE-2025-54127

HAXcms with nodejs backend allows users to start the server in any HAXsite or HAXcms instance. In versions 11.0.6 and below, the NodeJS version of HAXcms uses an insecure default configuration designed for local development. The default configuration does not perform authorization or authentication checks. If a user were to deploy haxcms-nodejs without modifying the default settings, ‘HAXCMS_DISABLE_JWT_CHECKS‘ would be set to ‘true‘ and their deployment would lack session authentication. This is fixed in version 11.0.7.
CVSS

No CVSS.

Configurations

No configuration.

History

22 Jul 2025, 13:05

Type Values Removed Values Added
Summary
  • (es) HAXcms con backend de NodeJS permite a los usuarios iniciar el servidor en cualquier HAXsite o instancia de HAXcms. En las versiones 11.0.6 y anteriores, la versión de NodeJS de HAXcms utiliza una configuración predeterminada insegura, diseñada para el desarrollo local. Esta configuración predeterminada no realiza comprobaciones de autorización ni autenticación. Si un usuario implementara haxcms-nodejs sin modificar la configuración predeterminada, 'HAXCMS_DISABLE_JWT_CHECKS' se establecería en 'true' y su implementación carecería de autenticación de sesión. Esto se solucionó en la versión 11.0.7.

21 Jul 2025, 22:15

Type Values Removed Values Added
Summary (en) HAXcms with nodejs backend allows users to start the server in any HAXsite or HAXcms instance. In versions 11.0.6 and below, the NodeJS version of HAX CMS uses an insecure default configuration designed for local development. The default configuration does not perform authorization or authentication checks. If a user were to deploy haxcms-nodejs without modifying the default settings, ‘HAXCMS_DISABLE_JWT_CHECKS‘ would be set to ‘true‘ and their deployment would lack session authentication. This is fixed in version 11.0.7. (en) HAXcms with nodejs backend allows users to start the server in any HAXsite or HAXcms instance. In versions 11.0.6 and below, the NodeJS version of HAXcms uses an insecure default configuration designed for local development. The default configuration does not perform authorization or authentication checks. If a user were to deploy haxcms-nodejs without modifying the default settings, ‘HAXCMS_DISABLE_JWT_CHECKS‘ would be set to ‘true‘ and their deployment would lack session authentication. This is fixed in version 11.0.7.

21 Jul 2025, 21:15

Type Values Removed Values Added
New CVE

Information

Published : 2025-07-21 21:15

Updated : 2025-07-22 13:05


NVD link : CVE-2025-54127

Mitre link : CVE-2025-54127

CVE.ORG link : CVE-2025-54127


JSON object : View

Products Affected

No product.

CWE
CWE-1188

Initialization of a Resource with an Insecure Default