CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-63012

CVE-2026-63012: Authorization Bypass and Information Disclosure in baserCMS Administrative API

Alon Barad
Alon Barad
Software Engineer

Nov 20, 2026·9 min read·0 visits

Executive Summary (TL;DR)

Authenticated baserCMS operators can bypass JWT requirements on administrative API endpoints via a session fallback mechanism triggered by the HTTP Referer header, exposing restricted site configurations and infrastructure settings.

CVE-2026-63012 is an authorization bypass and information disclosure vulnerability in baserCMS versions prior to 5.3.0. An architectural flaw in the authentication service configuration combined with overly permissive API access control rules allows low-privileged operator accounts to query restricted administrative API endpoints by supplying a matching HTTP Referer header.

Vulnerability Overview

baserCMS is an open-source content management system and web application development framework built on CakePHP. Within its core architecture (baserproject/baser-core), the application separates user interaction into distinct routing and authentication prefixes, primarily Admin for the server-rendered administrative interface and Api/Admin for the RESTful administrative API. Users assigned to the operator group are granted restricted operational permissions within the Admin web interface, while full system administrators hold unrestricted access across both web and API interfaces.

In baserCMS versions prior to 5.3.0, an authorization bypass vulnerability exists within the Api/Admin routing prefix that allows low-privileged operator accounts to access administrator-restricted API endpoints. By design, operator accounts are restricted to the Admin authentication prefix in UsersTable.php and cannot obtain a valid JSON Web Token (JWT) for the Api/Admin prefix. However, the authentication service definition in BaserCorePlugin::getAuthenticationService() implements a conditional fallback to cookie-based session authentication when an incoming request contains an HTTP Referer header matching the host origin.

When this session fallback is triggered, the application authenticates the API request using the operator's active web session. Because several sensitive administrative API endpoints in plugins/baser-core/config/permission.php were configured with 'auth' => true (requiring only valid authentication) rather than 'auth' => false (restricting access strictly to full system administrators), the authorization check succeeds for operator sessions.

Tracked as CVE-2026-63012 (GHSA-wgvx-x5g3-9v29) and classified under CWE-290 (Authentication Bypass by Spoofing), this flaw enables authenticated operators to extract sensitive global site configurations, mail parameters, and multi-site infrastructure settings from endpoints such as /baser/api/admin/baser-core/site_configs/view.json.

Root Cause Analysis

The root cause of CVE-2026-63012 is the combination of an HTTP header-dependent authentication fallback mechanism and inconsistent permission definitions between the web UI and the REST API. In baserCMS, the Api/Admin prefix defaults to JWT authentication (setupJwtAuth). Because the administrative single-page application (SPA) components running inside the web control panel make asynchronous requests to Api/Admin endpoints without managing separate JWT lifecycles, developers introduced a fallback in BaserCorePlugin::getAuthenticationService() to load CakePHP's Authentication.Session authenticator whenever BcUtil::isSameReferrerAsCurrent() evaluated to true.

Relying on BcUtil::isSameReferrerAsCurrent() as a security boundary is structurally flawed because the HTTP Referer header is controlled by the client and automatically attached by browsers during same-origin fetch() or XMLHttpRequest calls. Moreover, the Authentication.Session authenticator validates the session stored under the configured sessionKey (AuthAdmin), which is populated for both full administrators and low-privileged operators upon logging into the administrative dashboard. Consequently, any request from an authenticated operator bearing a same-origin Referer header satisfies the Api/Admin authentication layer, bypassing the prefix restriction enforced during JWT issuance.

Once authenticated, the request is evaluated by the permission control layer using rules defined in plugins/baser-core/config/permission.php. In baserCMS permission mappings, 'auth' => false denotes that default authenticated access is denied unless the user belongs to the super-administrator group (or an explicit permission rule is added in the database), whereas 'auth' => true grants implicit access to any user who passes authentication.

While the web UI controllers for system configuration (SiteConfigs) and multi-site administration (Sites) were restricted with 'auth' => false, four corresponding read endpoints in the Api/Admin configuration were inadvertently set to 'auth' => true. Because the session fallback bridged the Admin session into the Api/Admin context, the 'auth' => true configuration permitted low-privileged operators to invoke these endpoints directly.

Code Analysis

The vulnerability and its remediation span four primary files in the baser-core plugin: plugins/baser-core/config/permission.php, plugins/baser-core/src/BaserCorePlugin.php, plugins/baser-core/src/Controller/Api/Admin/BcAdminApiController.php, and plugins/baser-core/src/Utility/BcUtil.php. The primary remediation was committed in 2d7f74d3d5d584b9478c210016b81a1b7c30e9fb for the 5.3.0 release and backported to the 5.2.x branch in 464227b8770704076ee6eddd4bd464c184786eca.

First, in plugins/baser-core/config/permission.php, the read endpoints for SiteConfigs and Sites under the Api/Admin prefix were modified from 'auth' => true to 'auth' => false to align API access controls with the administrative web interface:

--- a/plugins/baser-core/config/permission.php
+++ b/plugins/baser-core/config/permission.php
@@ -283,7 +283,7 @@
             'items' => [
                 'CheckSendmail' => ['title' => __d('baser_core', 'メール送信テスト'), 'url' => '/baser/api/admin/baser-core/site_configs/check_sendmail.json', 'method' => 'POST', 'auth' => false],
                 'Edit' => ['title' => __d('baser_core', '編集'), 'url' => '/baser/api/admin/baser-core/site_configs/edit.json', 'method' => 'POST', 'auth' => false],
-                'View' => ['title' => __d('baser_core', '設定取得'), 'url' => '/baser/api/admin/baser-core/site_configs/view.json', 'method' => 'GET', 'auth' => true],
+                'View' => ['title' => __d('baser_core', '設定取得'), 'url' => '/baser/api/admin/baser-core/site_configs/view.json', 'method' => 'GET', 'auth' => false],
             ]
         ],
@@ -295,9 +295,9 @@
                 'Add' => ['title' => __d('baser_core', '新規登録'), 'url' => '/baser/api/admin/baser-core/sites/add.json', 'method' => 'POST', 'auth' => false],
                 'Delete' => ['title' => __d('baser_core', '削除'), 'url' => '/baser/api/admin/baser-core/sites/delete/*.json', 'method' => 'POST', 'auth' => false],
                 'Edit' => ['title' => __d('baser_core', '編集'), 'url' => '/baser/api/admin/baser-core/sites/edit/*.json', 'method' => 'POST', 'auth' => false],
-                'GetSelectableDevicesAndLang' => ['title' => __d('baser_core', '選択可能な言語とデバイス取得'), 'url' => '/baser/api/admin/baser-core/sites/get_selectable_devices_and_lang/*.json', 'method' => 'GET', 'auth' => true],
-                'Index' => ['title' => __d('baser_core', '一覧取得'), 'url' => '/baser/api/admin/baser-core/sites/index.json', 'method' => 'GET', 'auth' => true],
-                'View' => ['title' => __d('baser_core', '単一取得'), 'url' => '/baser/api/admin/baser-core/sites/view/*.json', 'method' => 'GET', 'auth' => true],
+                'GetSelectableDevicesAndLang' => ['title' => __d('baser_core', '選択可能な言語とデバイス取得'), 'url' => '/baser/api/admin/baser-core/sites/get_selectable_devices_and_lang/*.json', 'method' => 'GET', 'auth' => false],
+                'Index' => ['title' => __d('baser_core', '一覧取得'), 'url' => '/baser/api/admin/baser-core/sites/index.json', 'method' => 'GET', 'auth' => false],
+                'View' => ['title' => __d('baser_core', '単一取得'), 'url' => '/baser/api/admin/baser-core/sites/view/*.json', 'method' => 'GET', 'auth' => false],
             ]
         ],

Second, in plugins/baser-core/src/BaserCorePlugin.php, the spoofable BcUtil::isSameReferrerAsCurrent() condition was removed from getAuthenticationService(). Instead of treating the Referer header as an authentication gate, the application now unconditionally registers Authentication.Session for Api/Admin so that internal SPA requests work consistently while relying on permission.php and controller checks for authorization:

--- a/plugins/baser-core/src/BaserCorePlugin.php
+++ b/plugins/baser-core/src/BaserCorePlugin.php
@@ -510,8 +510,12 @@ public function getAuthenticationService(ServerRequestInterface $request): Authe
                 break;
             case 'Jwt':
                 $this->setupJwtAuth($service, $authSetting, $prefix);
-                if ($prefix === 'Api/Admin' && BcUtil::isSameReferrerAsCurrent()) {
-                    // セッションを持っている場合もログイン状態とみなす
+                if ($prefix === 'Api/Admin') {
+                    // GHSA-wgvx-x5g3-9v29: Remove spoofable Referer check (CWE-290)
+                    // Always load Session authenticator for admin SPA (runs via session cookies).
                     $service->loadAuthenticator('Authentication.Session', [
                         'sessionKey' => $authSetting['sessionKey'],
                     ]);

Third, in plugins/baser-core/src/Controller/Api/Admin/BcAdminApiController.php, the beforeFilter() gate check—which blocks external API usage when the environment variable USE_CORE_ADMIN_API is set to false—previously relied on BcUtil::isSameReferrerAsCurrent(). This allowed external JWT callers to bypass the USE_CORE_ADMIN_API=false restriction simply by spoofing the Referer header. The patch replaces the Referer check with an explicit verification that the active authentication provider is an instance of SessionAuthenticator:

--- a/plugins/baser-core/src/Controller/Api/Admin/BcAdminApiController.php
+++ b/plugins/baser-core/src/Controller/Api/Admin/BcAdminApiController.php
@@ -63,9 +63,13 @@ public function beforeFilter(EventInterface $event)
         }
 
         // Gate check: If Admin API is disabled via USE_CORE_ADMIN_API=false,
-        // only allow AJAX from admin SPA. Replaced Referer check with provider check:
         if (!filter_var(env('USE_CORE_ADMIN_API', false), FILTER_VALIDATE_BOOLEAN)) {
-            if (!BcUtil::isSameReferrerAsCurrent()) {
+            $provider = $this->Authentication->getAuthenticationService()->getAuthenticationProvider();
+            if (!($provider instanceof SessionAuthenticator)) {
                 throw new ForbiddenException(__d('baser_core', 'baser Admin APIは許可されていません。'));
             }
         }

Finally, plugins/baser-core/src/Utility/BcUtil.php was updated to add BcUtil::isSameOriginAsCurrent(), which normalizes and compares $_SERVER['HTTP_ORIGIN'] (falling back to $_SERVER['HTTP_REFERER']) against the current scheme and HTTP_HOST. This addresses related permissive regular expression bypasses (CWE-625 / GHSA-gwfr-7r8h-c5mp) in origin validation.

Exploitation

Exploiting CVE-2026-63012 requires low-privileged authentication (PR:L) as a user assigned to the operator group (or any custom non-administrator group lacking explicit API access). No user interaction (UI:N) or complex timing conditions (AC:L) are required.

To execute the attack, the operator logs into the baserCMS administrative panel at /baser/admin/users/login, establishing a valid AuthAdmin session cookie in their browser or HTTP client. Because the session authenticator fallback is triggered whenever the HTTP Referer header matches the target application's domain, the attacker can issue direct HTTP GET requests to the vulnerable API endpoints.

When executed from the browser developer console while authenticated as an operator, the browser automatically includes the session cookie and sets a same-origin Referer header:

fetch('/baser/api/admin/baser-core/site_configs/view.json', {
  headers: {
    'Referer': location.origin + '/baser/admin/' 
  }
})
.then(r => r.json())
.then(d => {
  console.table(d.siteConfig);
});

Alternatively, an attacker using an external HTTP client such as curl can supply the stolen or active session cookie along with a crafted Referer header:

curl -s -X GET "https://target.example.com/baser/api/admin/baser-core/site_configs/view.json" \
  -H "Cookie: CAKEPHP=<operator_session_id>" \
  -H "Referer: https://target.example.com/baser/admin/"

The server responds with an HTTP 200 status and a JSON payload containing the full siteConfig object, or site configuration listings when querying /baser/api/admin/baser-core/sites/index.json, /baser/api/admin/baser-core/sites/view/*.json, and /baser/api/admin/baser-core/sites/get_selectable_devices_and_lang/*.json.

Impact Assessment

CVE-2026-63012 carries a CVSS v3.1 base score of 6.5 (Medium) with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. The impact is strictly limited to confidentiality (C:H), with no direct integrity (I:N) or availability (A:N) impact because the misconfigured entries in permission.php only applied to read-only GET endpoints (View, Index, and GetSelectableDevicesAndLang). State-changing POST endpoints such as Edit, Add, Delete, and CheckSendmail were already configured with 'auth' => false prior to the patch.

By querying /baser/api/admin/baser-core/site_configs/view.json, an authenticated operator obtains the global siteConfig data structure. In baserCMS, site_configs stores system-wide configuration parameters, including administrative email addresses, SMTP server hostnames, ports, usernames, and authentication credentials, external service API keys, maintenance mode flags, and internal system settings.

Additionally, querying /baser/api/admin/baser-core/sites/index.json and /baser/api/admin/baser-core/sites/view/*.json exposes the configuration of all sub-sites managed by the baserCMS instance, including domain mappings, aliases, theme assignments, and language/device routing settings.

> [!NOTE] > While CVE-2026-63012 does not directly permit administrative state modification, disclosure of SMTP credentials or third-party API tokens stored in site_configs can enable secondary lateral movement or privilege escalation depending on the target environment.

Remediation

Site administrators and developers using baserCMS should upgrade to baserCMS 5.3.0 or apply the backported security commits to the 5.2.x maintenance branch (2d7f74d3d5d584b9478c210016b81a1b7c30e9fb / 464227b8770704076ee6eddd4bd464c184786eca). Updating via Composer (composer update baserproject/baser-core) pulls the updated permission mappings and authentication service logic.

For environments where an immediate version upgrade is not feasible, administrators can apply a manual configuration hotfix directly to plugins/baser-core/config/permission.php. Locate the SiteConfigsAdminApi and SitesAdminApi rule definitions under the Api/Admin prefix and change 'auth' => true to 'auth' => false for the View, Index, and GetSelectableDevicesAndLang items.

Additionally, organizations should audit web server access logs and application logs for unexpected GET requests to /baser/api/admin/baser-core/site_configs/view.json and /baser/api/admin/baser-core/sites/* originating from sessions associated with non-administrative operator accounts.

If external credentials such as SMTP passwords or API keys are stored within the baserCMS site configuration and untrusted operator accounts had access to the system prior to patching, those credentials should be rotated as a precautionary measure.

Official Patches

baserprojectbaserCMS 5.3.0 Release Notes
baserprojectGitHub Security Advisory GHSA-wgvx-x5g3-9v29

Fix Analysis (2)

Technical Appendix

CVSS Score
6.5/ 10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected Systems

baserproject/basercmsbaserproject/baser-core

Affected Versions Detail

Product
Affected Versions
Fixed Version
baser-core
baserproject
< 5.3.05.3.0
basercms
baserproject
< 5.3.05.3.0
AttributeDetail
CVE IDCVE-2026-63012
GHSA IDGHSA-wgvx-x5g3-9v29
CWECWE-290 (Authentication Bypass by Spoofing)
CVSS v3.1 Score6.5 Medium (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)
Attack VectorNetwork (Authenticated Low-Privileged Operator)
ImpactHigh Confidentiality Loss (Administrative Site Configuration Disclosure)
Exploit StatusPublic PoC Available
CISA KEV StatusNot Listed

MITRE ATT&CK Mapping

T1078.003Valid Accounts: Local Accounts
Privilege Escalation
T1556Modify Authentication Process
Defense Evasion
T1552Unsecured Credentials
Credential Access
CWE-290
Authentication Bypass by Spoofing

The software must verify the identity of an actor, but it uses an entity-controlled attribute (such as an HTTP Referer header) as proof of identity or authorization context.

Known Exploits & Detection

GitHub Security AdvisoryOfficial proof-of-concept JavaScript fetch snippet demonstrating unauthorized retrieval of site_configs/view.json by an operator session.

Vulnerability Timeline

Initial backport patch developed for 5.2.x branch (commit 464227b8770704076ee6eddd4bd464c184786eca)
2026-07-23
Core patch merged into 5.3.0 release line (commit 2d7f74d3d5d584b9478c210016b81a1b7c30e9fb)
2026-07-30
CVE-2026-63012 and GHSA-wgvx-x5g3-9v29 published
2026-11-19
Advisory metadata synchronized across NVD and OSV
2026-11-20

References & Sources

  • [1]GitHub Security Advisory: GHSA-wgvx-x5g3-9v29
  • [2]CVE.org Record: CVE-2026-63012
  • [3]National Vulnerability Database: CVE-2026-63012
  • [4]GitHub Fix Commit (5.3.0): 2d7f74d3d5d584b9478c210016b81a1b7c30e9fb
  • [5]GitHub Backport Commit (5.2.x): 464227b8770704076ee6eddd4bd464c184786eca
  • [6]baserCMS 5.3.0 Release Tag
  • [7]CVEListV5 Record for CVE-2026-63012

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•about 2 hours ago•CVE-2026-102945
4.9

CVE-2026-102945: Unrecovered Goroutine Panic via Malformed NGAP PathSwitchRequest in Aether Project AMF

CVE-2026-102945 is a denial-of-service vulnerability affecting the Access and Mobility Management Function (AMF) of the Aether Project (omec-project/amf) prior to version 3.1.6. When processing an NGAP PathSwitchRequest message over the 3GPP N2 interface, the HandlePathSwitchRequest function fails to verify the byte slice lengths of extensible APER bit strings inside the UESecurityCapabilities Information Element before accessing index zero. Because the NGAP receive goroutine lacks a panic recovery handler, supplying a zero-length bit string triggers an out-of-bounds slice read panic that terminates the entire AMF daemon.

Amit Schendel
Amit Schendel
1 views•11 min read
•about 3 hours ago•CVE-2026-103025
8.7

CVE-2026-103025: Unbounded Memory Allocation and Decompression Bomb in bep/imagemeta PNG Parser

CVE-2026-103025 (GHSA-7hvw-3c2q-45qg) is a high-severity denial-of-service (DoS) vulnerability in github.com/bep/imagemeta prior to version 0.17.3. The PNG metadata parser fails to validate declared chunk lengths prior to heap buffer allocation (CWE-789) and inflates zlib-compressed zTXt IPTC chunks without an output size limit (CWE-409). Additionally, out-of-bounds slice indexing in the PNG zTXt handler and IPTC character set resolver allows remote attackers to trigger runtime panics.

Amit Schendel
Amit Schendel
1 views•1 min read
•about 4 hours ago•CVE-2026-103033
5.3

CVE-2026-103033: Pre-Verification Nil-Map Panic and Denial of Service in ALTCHA Go Library

CVE-2026-103033 (GHSA-gfwj-45pc-w6r5) is an unauthenticated pre-verification Denial of Service (DoS) vulnerability in the Go implementation of the ALTCHA bot-prevention library (github.com/altcha-org/altcha-lib-go). In versions 2.0.0 and 2.0.1, the internal function parseServerSignature conditionally initializes the ServerSignatureVerificationData.Extra map only when url.ParseQuery returns no error. When an attacker submits a payload containing both an unrecognized query parameter and malformed percent-encoding in the VerificationData field, url.ParseQuery returns partially parsed parameters alongside an error. Because execution continues without initializing the Extra map, the subsequent loop attempts to write unknown parameters into a nil map, triggering a fatal Go runtime panic before cryptographic signature verification occurs.

Alon Barad
Alon Barad
2 views•10 min read
•about 5 hours ago•CVE-2026-114516
9.8

CVE-2026-114516: Pre-Authentication Path Traversal and Arbitrary File Read in Etherpad

A pre-authentication path traversal vulnerability exists in Etherpad versions 1.8.14 prior to 3.3.3 within the `/static/*` plugin asset handler. In `src/node/utils/Minify.ts`, an unconditional backslash-to-forward-slash conversion is executed after pathname sanitization has already concluded. On POSIX systems, this transforms benign backslash characters into directory traversal sequences (`../`), allowing unauthenticated remote attackers to read arbitrary files from the host filesystem, extract administrative credentials from `settings.json`, and achieve remote code execution via the plugin installation interface.

Alon Barad
Alon Barad
3 views•10 min read
•about 6 hours ago•CVE-2026-128135
7.1

CVE-2026-128135: Sandbox Escape and Arbitrary File Overwrite via Hardlink Following in NLTK ZIP Extraction

A local sandbox escape vulnerability exists in the Natural Language Toolkit (NLTK) versions 3.9.4 through 3.10.3 within its ZIP archive extraction implementation. Due to a type mismatch in member resolution and a failure to inspect filesystem link counts (st_nlink > 1), the extraction routine follows pre-planted hardlinks inside the extraction root, allowing a local attacker to truncate and overwrite arbitrary out-of-root files writable by the executing process.

Alon Barad
Alon Barad
5 views•10 min read
•about 7 hours ago•CVE-2026-129304
5.4

CVE-2026-129304: Improper Input Validation and Redis Glob Injection in Guard Core

CVE-2026-129304 is an improper input validation and Redis glob pattern injection vulnerability in Guard Core versions 1.0.0 through 3.12.0. The header parsing routine _extract_from_forwarded_header() extracts values from the X-Forwarded-For HTTP header without verifying that the extracted substring is a valid IPv4 or IPv6 address. In deployments configured with trusted_proxies where the target header index is client-controllable, arbitrary strings containing Redis glob metacharacters reach BehaviorTracker and are interpolated directly into Redis key names and blocking KEYS queries. This allows unauthenticated attackers to aggregate cross-client behavioral metrics, trigger false-positive rate limits, cause denial of service via O(N) Redis keyspace scans, or raise unhandled ValueError exceptions during automated IP ban operations.

Amit Schendel
Amit Schendel
4 views•10 min read