CVE-2018-0572: baserCMS Access Control Bypass

baserproject/basercms Updated 02 Oct 2025

Summary

13/05/2022
Yes i
High
8.1

CVE-2018-0572: baserCMS vulnerable to Access Control Bypass. Affects baserproject/basercms across 2 version ranges.

< 3.0.16 >= 4.0.0, < 4.1.1

Fixed in 3.0.16 or 4.1.1, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

baserCMS is an open-source content management system (CMS) developed by baserproject. It provides a platform for creating and managing websites, allowing users to publish and organize content. The vulnerability identified as CVE-2018-0572 affects baserCMS versions 4.1.0.1 and earlier, as well as versions 3.0.15 and earlier. This vulnerability allows remote authenticated attackers to bypass access restrictions and gain unauthorized access to restricted content within the CMS.

Vulnerability Detail

The vulnerability in baserCMS allows remote authenticated attackers to bypass access restrictions and view or alter restricted content. The specific vectors through which this bypass can occur are unspecified. This vulnerability poses a significant risk as it enables unauthorized access to sensitive information and potentially allows malicious actors to modify or delete important content within the CMS. The impact of this vulnerability can vary depending on the nature of the restricted content and the privileges of the authenticated user.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 3.0.16 3.0.16
    composer require baserproject/basercms:3.0.16
  • >= 4.0.0, < 4.1.1 4.1.1
    composer require baserproject/basercms:4.1.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

No specific workaround has been provided for this vulnerability. The recommended course of action is to apply the available patches or upgrade to the fixed versions as mentioned in the 'how_to_fix' section.

Conclusion

The baserCMS vulnerability identified as CVE-2018-0572 allows remote authenticated attackers to bypass access restrictions and gain unauthorized access to restricted content. To mitigate this vulnerability, it is crucial to upgrade to the patched versions of baserCMS or apply the available fixes. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for baserproject/basercms →

Share this vulnerability

FAQ

baserCMS is an open-source content management system developed by baserproject. It provides a platform for creating and managing websites.

The vulnerability affects baserCMS versions 4.1.0.1 and earlier, as well as versions 3.0.15 and earlier.

Remote authenticated attackers can exploit this vulnerability to bypass access restrictions and gain unauthorized access to restricted content within baserCMS.

The impact of this vulnerability can vary depending on the nature of the restricted content and the privileges of the authenticated user. It can lead to unauthorized access to sensitive information and potential modification or deletion of important content within the CMS.

To fix this vulnerability, users should upgrade to the patched versions of baserCMS (4.1.1 or later for baserCMS 4.x, and 3.0.16 or later for baserCMS 3.x). Detailed upgrade instructions can be found on the official baserCMS website.

Related vulnerabilities

Recent vulnerabilities recorded for baserproject/basercms.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 3.0.16 3.0.16
    composer require baserproject/basercms:3.0.16
  • >= 4.0.0, < 4.1.1 4.1.1
    composer require baserproject/basercms:4.1.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback