CVE-2026-63012: baserCMS administrative API authorization bypass through session fallback

Medium CVSS 6.5

OSV id
GHSA-wgvx-x5g3-9v29
Also known as
CVE-2026-63012
Published
Last modified

Affected packages

PackageAffected versionsFixed in
baserproject/baser-core
Packagist
< 5.3.0 5.3.0

How to fix it

Upgrade baserproject/baser-core to 5.3.0 or later.

composer update baserproject/baser-core
# if composer.json blocks it: composer require "baserproject/baser-core:^5.3.0"
  • If it is an indirect dependency, `composer update` the package that requires it, with dependencies.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

Summary

An authorization bypass occurs against the API endpoint /baser/api/admin/ by abusing the session authentication fallback.

Details

The mail settings are used here as an example.

Admin side:

https://github.com/baserproject/basercms/blob/master/plugins/baser-core/config/permission.php#L100 With auth => false, it is not accessible with operator privileges.

API side:

https://github.com/baserproject/basercms/blob/master/plugins/baser-core/config/permission.php#L286 With auth => true, it is accessible even with operator privileges.


First, the default group for operators has auth_prefix = 'Admin', which does not include Api/Admin.

https://github.com/baserproject/basercms/blob/master/plugins/baser-core/src/Model/Table/UsersTable.php#L389

Because of this condition, when trying to access the Api/Admin API with a JWT, operators have auth_prefix = 'Admin', so they cannot obtain a JWT and should not be able to access it.

However, there is a problem in getAuthenticationService.

https://github.com/baserproject/basercms/blob/master/plugins/baser-core/src/BaserCorePlugin.php#L507

Here, session authentication is enabled even for the Api/Admin prefix. By accessing the API with a Referer header, session authentication becomes active, allowing access to the API without holding a JWT.

As a result, all APIs configured with auth => true in permission.php become accessible by operators.

PoC
  1. Log in with a site operator (operator) privileged account.
  2. Run the following code in DevTools:
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);
})

<img width="1886" height="1027" alt="Screenshot_20260404_075242" src="https://github.com/user-attachments/assets/e91a1d27-ac36-42fb-88a8-bc699b28b04f" />

<img width="1277" height="595" alt="Screenshot_20260404_075133" src="https://github.com/user-attachments/assets/9c54459a-dad0-4445-a35d-1373255c2b22" />

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.