{"id":59821,"date":"2025-08-02T09:33:20","date_gmt":"2025-08-02T09:33:20","guid":{"rendered":""},"modified":"2025-09-10T13:08:01","modified_gmt":"2025-09-10T19:08:01","slug":"cve-2025-54378-unauthorized-access-vulnerability-in-hax-cms","status":"publish","type":"post","link":"https:\/\/www.ameeba.com\/blog\/cve-2025-54378-unauthorized-access-vulnerability-in-hax-cms\/","title":{"rendered":"<strong>CVE-2025-54378: Unauthorized Access Vulnerability in HAX CMS<\/strong>"},"content":{"rendered":"<p><strong>Overview<\/strong><\/p>\n<p>The CVE-2025-54378 is a critical vulnerability found in HAX CMS, a content management system (CMS) that allows you to manage your microsite universe with PHP or NodeJs backends. This vulnerability opens up the possibility of unauthorized access to resources through API endpoints, as they fail to perform necessary authorization checks. This can potentially <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-7793-critical-vulnerability-in-tenda-fh451-leading-to-system-compromise\/\"  data-wpil-monitor-id=\"69602\">lead to system<\/a> compromise or data leakage, putting users&#8217; data at serious risk. Given the <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-47998-severe-heap-based-buffer-overflow-vulnerability-in-windows-routing-and-remote-access-service\/\"  data-wpil-monitor-id=\"67352\">severity of this vulnerability<\/a>, it&#8217;s crucial for organizations using HAX CMS to understand its potential impact and take the necessary steps to mitigate it.<\/p>\n<p><strong>Vulnerability Summary<\/strong><\/p>\n<p>CVE ID: CVE-2025-54378<br \/>\nSeverity: High (8.3 CVSS Severity Score)<br \/>\nAttack Vector: Network<br \/>\nPrivileges Required: None<br \/>\nUser Interaction: None<br \/>\nImpact: System compromise or <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-53495-unauthorized-access-data-leakage-in-wikimedia-foundation-mediawiki-abusefilter-extension\/\"  data-wpil-monitor-id=\"72454\">data leakage<\/a><\/p>\n<p><strong>Affected Products<\/strong><\/p><div id=\"ameeb-1623619372\" class=\"ameeb-content-2 ameeb-entity-placement\"><div style=\"border-left: 4px solid #555; padding-left: 20px; margin: 48px 0; font-family: Roboto, sans-serif; color: #ffffff; line-height: 1.6; max-width: 720px;\">\r\n  <h2 style=\"margin-top: 0; font-size: 22px; font-weight: 600; display: flex; align-items: center; letter-spacing: -0.02em;\">\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\" style=\"display: inline-flex; align-items: center; margin-right: 10px;\">\r\n      <img decoding=\"async\" src=\"https:\/\/www.ameeba.com\/blog\/wp-content\/uploads\/2025\/10\/Best-App-icon-Ameeba.png\" alt=\"Ameeba Chat Icon\" style=\"width: 42px; height: 42px;\" \/>\r\n    <\/a>\r\n    Share secrets securely\r\n  <\/h2>\r\n\r\n  <p style=\"margin-bottom: 14px; color: #d1d5db;\">\r\n    Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.\r\n  <\/p>\r\n\r\n  <p style=\"margin-bottom: 18px; color: #a1a1aa;\">\r\n    Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.\r\n  <\/p>\r\n\r\n  <ul style=\"list-style: none; padding-left: 0; margin-bottom: 24px; color: #e4e4e7;\">\r\n    <li style=\"margin-bottom: 8px;\">\u2022 Encrypted identity<\/li>\r\n    <li style=\"margin-bottom: 8px;\">\u2022 Private Spaces for organizations and teams<\/li>\r\n    <li style=\"margin-bottom: 8px;\">\u2022 End-to-end encrypted chat, calls, files, and notes<\/li>\r\n    <li style=\"margin-bottom: 8px;\">\u2022 Sensitive AI work and protected collaboration<\/li>\r\n    <li>\u2022 Built for information that cannot leak<\/li>\r\n  <\/ul>\r\n\r\n  <p style=\"font-style: italic; font-weight: 600; margin-bottom: 24px; color: #ffffff;\">\r\n    Our mission is to secure human work alongside AI.\r\n  <\/p>\r\n\r\n  <div style=\"display: flex; flex-wrap: wrap; gap: 12px;\">\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\/download\" style=\"background-color: #ffffff; color: #000000; padding: 10px 20px; text-decoration: none; border-radius: 8px; font-weight: 500;\">\r\n      Download Ameeba\r\n    <\/a>\r\n\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\" style=\"border: 1px solid #ffffff; color: #ffffff; padding: 10px 20px; text-decoration: none; border-radius: 8px; font-weight: 500;\">\r\n      Learn More\r\n    <\/a>\r\n  <\/div>\r\n<\/div><\/div>\n<p>Product | Affected Versions<\/p>\n<p>haxcms-nodejs | 11.0.13 and below<br \/>\nhaxcms-php | 11.0.8 and below<\/p>\n<p><strong>How the Exploit Works<\/strong><\/p>\n<p>The vulnerability arises from the lack of authorization checks in the API endpoints of the <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-50067-critical-vulnerability-in-oracle-application-express-allowing-system-takeover\/\"  data-wpil-monitor-id=\"67353\">HAX<\/a> CMS application. While the <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-50738-memos-application-vulnerability-allows-for-unauthorized-user-information-disclosure\/\"  data-wpil-monitor-id=\"69601\">application does verify if a user<\/a> is authenticated, it does not check whether a user has the necessary authorization to interact with a certain resource. This means that an attacker, once authenticated, can interact with any resource within the application, potentially <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-41668-critical-file-replacement-leading-to-unauthorized-access\/\"  data-wpil-monitor-id=\"66324\">leading to unauthorized<\/a> access to sensitive data or even system compromise.<\/p>\n<p><strong>Conceptual Example Code<\/strong><\/p><div id=\"ameeb-3807153375\" class=\"ameeb-content ameeb-entity-placement\"><div class=\"poptin-embedded\" data-id=\"f6b387694f681\"><\/div>\r\n\r\n\r\n\r\n\r\n\r\n<\/div>\n<p>The lack of <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2024-7457-macos-authorization-model-exploit-leading-to-potential-mitm-attacks\/\"  data-wpil-monitor-id=\"80112\">authorization checks could be exploited<\/a> as follows:<\/p>\n<pre><code class=\"\" data-line=\"\">POST \/api\/resource-endpoint HTTP\/1.1\nHost: vulnerable-haxcms.example.com\nContent-Type: application\/json\nAuthorization: Bearer {valid-authentication-token}\n{ &quot;operation&quot;: &quot;delete&quot;, &quot;resource_id&quot;: &quot;sensitive_resource&quot; }<\/code><\/pre>\n<p>In this example, an attacker uses a valid <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-55306-critical-api-key-and-authentication-token-exposure-in-genx-fx-trading-platform\/\"  data-wpil-monitor-id=\"81368\">authentication token<\/a> (which could be obtained through various means) to send a request to delete a sensitive resource. Since the application does not check if the user has the necessary authorization to perform this operation, the request is executed, leading to <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-36600-dell-bios-improper-access-control-vulnerability-allows-potential-system-compromise\/\"  data-wpil-monitor-id=\"70139\">potential data loss or system<\/a> compromise.<\/p>\n<p><strong>Mitigation Guidance<\/strong><\/p>\n<p>To mitigate this vulnerability, users are recommended to update their HAX CMS to versions 11.0.14 of haxcms-nodejs and 11.0.9 of haxcms-php, where this issue has been fixed. As a temporary measure, users could also employ a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) to monitor and block suspicious requests.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview The CVE-2025-54378 is a critical vulnerability found in HAX CMS, a content management system (CMS) that allows you to manage your microsite universe with PHP or NodeJs backends. This vulnerability opens up the possibility of unauthorized access to resources through API endpoints, as they fail to perform necessary authorization checks. This can potentially lead [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"footnotes":""},"categories":[1],"tags":[],"vendor":[],"product":[],"attack_vector":[],"asset_type":[],"severity":[],"exploit_status":[],"class_list":["post-59821","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/59821","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/comments?post=59821"}],"version-history":[{"count":7,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/59821\/revisions"}],"predecessor-version":[{"id":73817,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/59821\/revisions\/73817"}],"wp:attachment":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/media?parent=59821"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/categories?post=59821"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/tags?post=59821"},{"taxonomy":"vendor","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/vendor?post=59821"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/product?post=59821"},{"taxonomy":"attack_vector","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/attack_vector?post=59821"},{"taxonomy":"asset_type","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/asset_type?post=59821"},{"taxonomy":"severity","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/severity?post=59821"},{"taxonomy":"exploit_status","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/exploit_status?post=59821"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}