# CVE-2018-0573: baserCMS Access Control Bypass

> Remote attackers can bypass access restrictions to view files uploaded by site users in baserCMS.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-33fq-qm4m-cjw3

## What is CVE-2018-0573?

CVE-2018-0573 is a medium-severity missing authorization vulnerability in Basercms Basercms, published on 26 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

baserCMS (baserCMS 4.1.0.1 and earlier versions, baserCMS 3.0.15 and earlier versions) allows remote attackers to bypass access restriction for a content to view a file which is uploaded by a site user via unspecified vectors.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2018-0573?

4 open source packages ship an affected version, including baserproject/basercms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `baserproject/basercms` | Packagist | All versions | 3.0.16 |
| `baserproject/basercms` | Packagist | All versions | 3.0.16 |
| `baserproject/basercms` | Packagist | From 4.0.0 | 4.1.1 |
| `baserproject/basercms` | Packagist | From 4.0.0 | 4.1.1 |

Products: Basercms Basercms.

## How do I fix CVE-2018-0573?

Upgrade baserproject/basercms to a fixed version for your release line: 3.0.16 or 4.1.1.

## Is CVE-2018-0573 being exploited?

There is no known exploitation of CVE-2018-0573 in the wild and no public exploit code.

## Other vulnerabilities in Basercms Basercms

- [CVE-2023-25654](https://insights.sbomify.com/CVE-2023-25654/): baserCMS File Uploader Remote Code Execution (RCE) vulnerability (critical 9.8)
- [CVE-2023-25655](https://insights.sbomify.com/CVE-2023-25655/): baserCMS allows any file to be uploaded (critical 9.8)
- [CVE-2017-10842](https://insights.sbomify.com/CVE-2017-10842/): baserCMS SQL Injection vulnerability (critical 9.8)
- [CVE-2026-30880](https://insights.sbomify.com/CVE-2026-30880/): baserCMS: OS command injection vulnerability in installer (critical 9.2)
- [CVE-2026-21861](https://insights.sbomify.com/CVE-2026-21861/): baserCMS: OS Command Injection Leading to Remote Code Execution (RCE) (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0573 and fix it if it is affected.

What it is: CVE-2018-0573 is a medium-severity missing authorization vulnerability in Basercms Basercms, published on 26 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0573 in the wild and no public exploit code.

Affected packages and fixed versions:
- baserproject/basercms (Packagist): affected all versions; fixed in 3.0.16
- baserproject/basercms (Packagist): affected all versions; fixed in 3.0.16
- baserproject/basercms (Packagist): affected from 4.0.0; fixed in 4.1.1
- baserproject/basercms (Packagist): affected from 4.0.0; fixed in 4.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-0573/ (Markdown: https://insights.sbomify.com/CVE-2018-0573/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-0573
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-0573
- OSV: https://osv.dev/vulnerability/CVE-2018-0573

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-0573/
Summaries are generated and may contain mistakes; the official description above is the record.