# CVE-2026-114623: baserCMS: Path traversal in the BcThemeFile admin screen allows file disclosure


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-rqr8-gmx5-xvrr

## What is CVE-2026-114623?

CVE-2026-114623 is a medium-severity vulnerability in baserproject basercms, published on 23 Oct 2026. 

### Official description

baserCMS is a website development framework. In versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2, an authenticated user with only theme-file view permission can traverse outside the theme directory through the optional BcThemeFile plugin's Admin web screen. ThemeFilesController::parseArgs() constructs a path containing literal ../ segments, and the view and edit actions pass it to ThemeFilesService::get() without containment validation. Authorization checks the unresolved request path, after which ThemeFile::_getContents() reads the resolved file and exposes its contents in the form textarea. A client must preserve the dot segments rather than normalize them away. Readable files are limited to .php, .css, .js, and .ctp; this can disclose application source and config/install.php database credentials in MySQL or PostgreSQL deployments, while SQLite configurations have an empty database password. Reading config/app_local.php may expose the Security.salt fallback, which is effective only when not overridden by environment configuration. The flaw does not disclose .env, .pem, or SQLite .db files, does not itself permit file writes or code execution, and does not affect the separate API getFullpath() route. The plugin is disabled by default and unauthenticated requests are not sufficient. This issue has been patched in versions 5.3.2 and 5.4.2.

Weakness: CWE-863 (Incorrect Authorization), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-114623?


## How do I fix CVE-2026-114623?

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

## Is CVE-2026-114623 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114623 and fix it if it is affected.

What it is: CVE-2026-114623 is a medium-severity vulnerability in baserproject basercms, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114623 in the wild and no public exploit code.

Affected product: baserproject basercms. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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