# CVE-2018-0570: XSS in baserCMS

> Remote authenticated attackers can inject arbitrary web script or HTML into baserCMS, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-994g-74gq-5qpr

## What is CVE-2018-0570?

CVE-2018-0570 is a medium-severity cross-site scripting vulnerability in Basercms Basercms, published on 26 Jun 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting vulnerability in baserCMS (baserCMS 4.1.0.1 and earlier versions, baserCMS 3.0.15 and earlier versions) allows remote authenticated attackers to inject arbitrary web script or HTML via unspecified vectors.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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 to 3.0.15 | None |
| `baserproject/basercms` | Packagist | All versions to 3.0.15 | None |
| `baserproject/basercms` | Packagist | From 4.0.0 to 4.1.0.1 | None |
| `baserproject/basercms` | Packagist | From 4.0.0 to 4.1.0.1 | None |

Products: Basercms Basercms.

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

No fix has been published for CVE-2018-0570 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-0570 being exploited?

There is no known exploitation of CVE-2018-0570 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-0570 and fix it if it is affected.

What it is: CVE-2018-0570 is a medium-severity cross-site scripting vulnerability in Basercms Basercms, published on 26 Jun 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-0570 in the wild and no public exploit code.

Affected packages and fixed versions:
- baserproject/basercms (Packagist): affected all versions up to 3.0.15; no fix listed
- baserproject/basercms (Packagist): affected all versions up to 3.0.15; no fix listed
- baserproject/basercms (Packagist): affected from 4.0.0 up to 4.1.0.1; no fix listed
- baserproject/basercms (Packagist): affected from 4.0.0 up to 4.1.0.1; no fix listed

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-0570/ (Markdown: https://insights.sbomify.com/CVE-2018-0570/index.md)
```

## Sources

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

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