/

CVE-2026-67960

Severity:

CRITICAL RISK

(9.8)

Code Injection (CWE-94) in PbootCMS Web Components

CVE-2026-67960

Deferred

Vulnerability type

Category:

Code Injection

CWE:

CWE-94

Impact:

Arbitrary 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

A critical code injection vulnerability in PbootCMS v3.2.15 affects multiple controller and helper components, including MemberController.php, UserController.php, CommentController.php, ContentController.php, and helper.php. An attacker who can reach a vulnerable execution path may be able to cause arbitrary code to run in the application's server-side context.

Affected context

The issue occurs in PbootCMS v3.2.15 deployments where the affected PHP controllers or helper functionality process attacker-influenced data in an unsafe execution context. Risk is higher when the application is publicly reachable and vulnerable request paths can be accessed without strong authorization controls.

Exploit preconditions

  • Attack surface: Web-accessible PbootCMS application endpoints
  • Required access: Ability to submit input that reaches one of the affected controllers or helper functions; authentication requirements may depend on deployment configuration
  • Trigger point: Processing of attacker-controlled data by vulnerable code in MemberController.php, UserController.php, CommentController.php, ContentController.php, or helper.php
  • Why exploitation is possible: Input may be interpreted as executable server-side logic rather than being handled strictly as data

Why this happens

The underlying bug is an unsafe code-generation or code-execution pattern in application logic. When attacker-controlled input reaches a dynamic execution sink without adequate separation from executable syntax, the application may interpret that input as PHP code. This behavior maps to CWE-94: Improper Control of Generation of Code, where externally influenced data can alter or create executable instructions.

Potential impact

  • An attacker may execute arbitrary code with the privileges of the web server process
  • Sensitive application data could be read, modified, or deleted
  • The application may be altered to host malicious content or create unauthorized accounts
  • Server credentials and connected service tokens could be exposed
  • A compromised application could enable lateral movement into connected systems

General mitigation guidance

Mitigation generally focuses on removing dynamic code execution from request-processing paths and ensuring that external input remains data.

Common defensive patterns include:

  • Replace dynamic evaluation or code generation with fixed, explicit control flow
  • Use allowlisted operations and strongly typed data structures for user-controlled values
  • Apply context-appropriate encoding and validation before data reaches interpreters or execution sinks
  • Separate administrative functionality from public request paths and enforce least-privilege authorization
  • Run the application with minimal filesystem, process, and database permissions
  • Restrict outbound network access and protect secrets from the web process

How teams detect issues like this

Organizations can look for code injection risks through:

  • Static analysis rules targeting dynamic PHP execution, runtime code generation, and unsafe interpreter calls
  • Code review checks for user-controlled data flowing into execution or evaluation sinks
  • Runtime monitoring for unexpected child processes, modified application files, or unusual outbound connections
  • Web application firewall and access-log policies identifying abnormal requests to affected controller paths
  • CI policies that reject newly introduced dynamic execution patterns and require security review for interpreter boundaries

Neutral automated code-review and software-composition tools may help identify related patterns, but findings should be validated against application-specific data flows.

Sources

SourceLink
github.comgithub.com/user-attachments/files/30816503/PbootCMS-3.2.15URL.Redirection.Vulnerability.docx
github.comgithub.com/xy-f0/CVE/issues/1#issue-4890245413

Frequently asked

questions

It may be remotely exploitable when the affected PbootCMS application is exposed through web-accessible request paths and attacker-controlled input can reach vulnerable code. The exact scope depends on endpoint exposure and authorization configuration.

Not necessarily. The description and critical network-oriented severity indicate that some deployments may expose a reachable path without authentication, but access requirements should be verified against the application's routing and access controls.

Remove dynamic code execution from the affected logic, treat all request data as untrusted, and replace interpreter-based behavior with fixed operations and strict allowlists.

Use secure coding standards that prohibit unsafe evaluation patterns, enforce least privilege, apply static analysis in CI, review data flows into execution sinks, and monitor production systems for unexpected process or file activity.

Find out what's already
exploitable in your codebase.