CVE-2026-63012 in BaserCMSinfo

Summary

by MITRE • 11/20/2026

baserCMS is a website development framework. Prior to 5.3.0, getAuthenticationService permits an Api/Admin session authentication fallback based on the Referer header, although operator accounts have an Admin auth prefix and cannot obtain an Api/Admin JWT. An authenticated operator can therefore access /baser/api/admin/ endpoints whose permission.php entries have auth => true, including /baser/api/admin/baser-core/site_configs/view.json, even when the corresponding administrative functionality is restricted. This can disclose administrator-restricted configuration information. This issue is fixed in 5.3.0.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified in baserCMS versions prior to 5.3.0 represents a critical authentication bypass flaw within its API administration layer, specifically affecting the getAuthenticationService mechanism. As an open-source website development framework based on CakePHP, baserCMS relies heavily on session management and token-based authentication for securing administrative interfaces. The core technical deficiency lies in how the application validates incoming requests against existing sessions when handling API endpoints designated for administrator access. Specifically, the system permits a fallback to Api/Admin session authentication that is improperly influenced by the HTTP Referer header. This design oversight allows an attacker who has already obtained valid operator-level credentials to manipulate this validation logic, effectively elevating their privileges or bypassing restrictions intended for higher-privileged administrative accounts.

The operational mechanics of this flaw exploit the distinction between different user roles within the CMS architecture. Operator accounts are typically assigned a specific authentication prefix that restricts them from obtaining Admin JSON Web Tokens (JWT), which are required to access sensitive administrative functions directly via standard API calls. However, due to the flawed logic in getAuthenticationService, an authenticated operator can trigger a fallback mechanism that validates their session against endpoints protected by auth => true configurations. This bypass is facilitated because the service incorrectly trusts contextual headers like Referer to determine authentication context rather than strictly enforcing token-based or role-based access controls. Consequently, operators gain unauthorized access to restricted API routes such as /baser/api/admin/baser-core/site_configs/view.json, which are explicitly designed to be inaccessible without proper administrative privileges.

The impact of this vulnerability is significant, primarily centering on the disclosure of sensitive configuration data that should remain hidden from lower-privileged users. By accessing endpoints like site_configs/view.json, an attacker can retrieve detailed information about the CMS installation, including database connection parameters, security keys, plugin configurations, and other environmental settings. This exposure not only violates the principle of least privilege but also provides attackers with valuable intelligence for further exploitation attempts, such as crafting targeted attacks against specific plugins or attempting to brute-force credentials using revealed configuration details. The ability to read administrator-restricted information undermines the integrity of the administrative interface and compromises the overall security posture of any baserCMS deployment running a vulnerable version.

This issue is classified under CWE-284 Improper Access Control, as it involves an actor bypassing established access control restrictions through flawed logic in authentication services. It also aligns with MITRE ATT&CK techniques related to Privilege Escalation and Discovery, where attackers leverage misconfigurations or bugs to gain unauthorized visibility into system configurations. The vulnerability highlights the dangers of relying on HTTP headers for security-critical decisions without rigorous validation against session state and role permissions.

To mitigate this risk, organizations running baserCMS must immediately upgrade to version 5.3.0 or later, where the getAuthenticationService logic has been corrected to prevent unauthorized fallbacks based on header manipulation. In addition to upgrading, administrators should ensure that their web servers are configured to strip or validate Referer headers appropriately if they are used for any non-critical routing purposes, although relying solely on this is not a recommended security practice. Regular audits of API endpoint permissions and strict enforcement of role-based access controls across all administrative interfaces are essential preventive measures against similar authentication bypass vulnerabilities in content management systems.

Responsible

GitHub M

Reservation

07/15/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00466

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!