baserCMS administrative API authorization bypass through session fallback
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.
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
- Log in with a site operator (operator) privileged account.
- 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);
})
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| Paczka Composer | baserproject/baser-core | < 5.3.0 | 5.3.0 |
Odnośniki
- https://github.com/baserproject/basercms/security/advisories/GHSA-wgvx-x5g3-9v29
- https://nvd.nist.gov/vuln/detail/CVE-2026-63012
- https://github.com/baserproject/basercms/commit/2d7f74d3d5d584b9478c210016b81a1b7c30e9fb
- https://github.com/baserproject/basercms/commit/464227b8770704076ee6eddd4bd464c184786eca
- https://github.com/baserproject/basercms
- https://github.com/baserproject/basercms/releases/tag/5.3.0
- Wektor CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- Słabość (CWE)
CWE-290- Platforma
- Composer
- Paczka
baserproject/baser-core- Ujawniono
- 20.11.2026
- Aktualizacja
- 20.11.2026 02:17
Źródła i licencje
OSV / GitHub Advisory Database - GHSA-wgvx-x5g3-9v29 - CC BY 4.0
Historia podatności: baserproject/baser-core
Wszystkie opisane podatności tej paczki (Paczka Composer), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 2
- Pierwsza → ostatnia
- 11.2026 11.2026
- Bez poprawki
- 0
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Wysoka 1
- Średnia 1
Ujawnienia w latach
- 2026: 2
-
baserCMS administrative API authorization bypass through session fallback ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.