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.
Published: 2026-10-23
Score: 6.5 Medium
EPSS: n/a
KEV: No
Impact: Information Disclosure
Action: Patch
AI Analysis

Impact

The vulnerability originates from the BcThemeFile plugin's admin screen, which allows an authenticated user with theme-file view permission to traverse outside the theme directory and read restricted files. The flaw relies on unvalidated path construction and omission of normalization, resulting in information disclosure of source code, configuration, and database credentials. This leads to a potential compromise of application secrets without granting write or execution rights.

Affected Systems

baserproject basercms versions 5.0.0 up to 5.3.1 and 5.4.0 up to 5.4.1 are affected. Versions 5.3.2 and 5.4.2 and later contain a fix. The plugin is disabled by default and does not provide unauthenticated access.

Risk and Exploitability

The CVSS score of 6.5 indicates a medium severity. EPSS is not available, suggesting limited or unquantified exploitation probability. The issue is not listed in the CISA KEV catalog. Exploitation requires an authenticated account with theme-file view rights, which is less privileged than full admin but still present. The attacker must maintain the dot segments in the request path to bypass normalization. If successful, the attacker can read .php, .css, .js, or .ctp files, including config/install.php and config/app_local.php, exposing database credentials and security salts. The vulnerability does not allow write or code execution, so the impact is limited to information disclosure.

Generated by OpenCVE AI on October 23, 2026 at 15:59 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the baserCMS update to version 5.3.2 or 5.4.2, which contains the fix.
  • Disable the BcThemeFile plugin for systems that do not require direct theme file viewing.
  • Restrict theme-file view permissions to only the minimum set of roles that need them.

Generated by OpenCVE AI on October 23, 2026 at 15:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 23 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 23 Oct 2026 14:00:00 +0000

Type Values Removed Values Added
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.
Title baserCMS: Path traversal in the BcThemeFile admin screen allows file disclosure
Weaknesses CWE-200
CWE-22
CWE-863
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-23T14:57:47.887Z

Reserved: 2026-10-21T20:34:25.600Z

Link: CVE-2026-114623

cve-icon Vulnrichment

Updated: 2026-10-23T14:48:57.217Z

cve-icon NVD

Status : Deferred

Published: 2026-10-23T14:17:51.430

Modified: 2026-10-23T16:28:32.357

Link: CVE-2026-114623

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-23T16:00:18Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-863

    Incorrect Authorization