/

CVE-2026-30880

Severity:

CRITICAL RISK

(9.8)

OS Command Injection in baserCMS Installer

CVE-2026-30880

Analyzed

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-78

Impact:

Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

baserCMS contained an OS command injection vulnerability in its installation component, allowing user-controlled input to influence shell command execution.

Under specific conditions during setup, an attacker could potentially run arbitrary system commands with the privileges of the web server or installer process.

Affected context

The vulnerability occurs in the baserCMS installation workflow, before a site is fully configured and hardened.

It is relevant in environments where:

  • The baserCMS installer is exposed over the network (e.g., a fresh deployment left accessible)
  • Installation parameters are accepted from HTTP requests and passed to system utilities
  • The hosting stack allows the PHP/web server user to invoke shell commands

Exploit preconditions

  • Attack surface: Web-based installer endpoint exposed via HTTP/HTTPS
  • Required access: Network-level ability to reach the installer (typically unauthenticated, depending on deployment)
  • Trigger point: Submission of crafted installation parameters that are later interpolated into shell or system calls
  • Why exploitation is possible: User-supplied values are incorporated into command-line strings without adequate validation, encoding, or separation from command syntax, enabling injection of additional commands or arguments

Why this happens

This issue stems from constructing OS command strings using untrusted installer input and executing them via shell-aware APIs.

When applications concatenate or interpolate raw user data into command lines (e.g., for database setup, file operations, or environment checks), the shell interprets special characters and metacharacters as control syntax.

This behavior maps to CWE-78: Improper Neutralization of Special Elements used in an OS Command, where insufficient sanitization or lack of parameterization allows attackers to break out of the intended command structure.

Potential impact

  • Execution of arbitrary system commands on the server
  • Complete compromise of the baserCMS instance and its data
  • Lateral movement within the hosting environment, depending on server configuration
  • Installation of backdoors or web shells during initial setup
  • Abuse of the compromised server to pivot into internal networks

General mitigation guidance

Mitigation generally focuses on eliminating direct shell command construction from untrusted input and tightening installer exposure:

  • Prefer high-level language APIs (e.g., database drivers, filesystem functions) instead of shelling out to system utilities
  • When OS commands are unavoidable, use parameterized execution interfaces that avoid passing through a command shell and treat arguments as data, not syntax
  • Apply strict validation and allowlists on all installer parameters that influence system operations
  • Restrict access to the installer to trusted administrators only (IP allowlisting, temporary authentication, or one-time tokens)
  • Run the web server and installer with least-privilege accounts that have limited access to the underlying OS and filesystem

How teams detect issues like this

Organizations can detect similar vulnerabilities and potential exploitation by:

  • Using static analysis rules to flag dynamic command construction (e.g., use of exec, system, shell_exec, backticks) that include user-controllable data
  • Incorporating secure coding checks into code review, focusing on installer and setup routines where shortcuts are common
  • Applying web application firewalls (WAF) with rules targeting common command injection patterns, understanding these are a defense-in-depth control
  • Monitoring server logs and process creation events for unusual commands spawned by the web server or PHP process, especially during installation windows

Sources

SourceLink
basercms.netbasercms.net/security/JVN_20837860
github.comgithub.com/baserproject/basercms/releases/tag/5.2.3
github.comgithub.com/baserproject/basercms/security/advisories/GHSA-6hpg-8rx3-cwgv

Frequently asked

questions

It can be, if the baserCMS installer is reachable over the network and not restricted to trusted administrators. An attacker who can access the installer interface during setup may be able to exploit the issue.

Typically, only network access to the installer endpoint is required. No prior authentication may be necessary, depending on how the installer is exposed and whether additional access controls were added by the operator.

Replace shell-based operations with safe, high-level language APIs wherever possible. When OS commands are unavoidable, use parameterized execution and strict allowlists, ensuring no raw user input is concatenated into command strings.

Establish secure coding standards that prohibit direct command construction from user input, enforce automated checks for command execution APIs, and subject installer/setup code to rigorous security review and testing before release.

Find out what's already
exploitable in your codebase.