CVE-2026-67960: An issue in PbootCMS v.3.2.15 allows an attacker to execute arbitrary code via the MemberController.php, Us...
An issue in PbootCMS v.3.2.15 allows an attacker to execute arbitrary code via the MemberController.php, UserController.php, CommentController.php, ContentController.php, and helper.php components
Security readout for executives and security teams
Plain-English summary
PbootCMS 3.2.15 is reported to permit unauthenticated remote arbitrary code execution through several application components. Successful exploitation could expose site data, allow unauthorized changes, or disrupt service. The supplied record rates it CVSS 9.8, but provides limited technical evidence and no confirmed fix.
Executive priority
Treat as an urgent exposure-assessment item because the reported impact is complete system compromise without authentication. Prioritize internet-facing PbootCMS 3.2.15 systems, but communicate that exploitation evidence and authoritative remediation details remain incomplete.
Technical view
The CVE describes CWE-94 code injection affecting MemberController.php, UserController.php, CommentController.php, ContentController.php, and helper.php. Its CVSS 3.1 vector indicates network access, low complexity, no privileges, and no user interaction, with high confidentiality, integrity, and availability impact. The precise vulnerable inputs and execution path are not documented.
Likely exposure
Internet-accessible deployments running PbootCMS 3.2.15 are the primary concern. The supplied structured affected-product data is incomplete, listing vendor, product, and versions as unavailable, so exposure beyond the version named in the description cannot be established.
Exploitation context
The supplied bundle does not establish active exploitation, and the CVE is not listed as KEV. Public references include a GitHub issue and document attachment, but the attachment title mentions URL redirection rather than code execution. Treat exploitation status and technical reproducibility as unconfirmed.
Researcher notes
The record lacks a documented root cause, vulnerable parameters, reproducible validation method, affected range, and fixed version. The structured affected field conflicts with the narrative by containing unavailable values. The reference attachment's redirection title also differs from the code-execution claim, warranting careful source validation without testing against production.
Mitigation direction
Identify and prioritize all PbootCMS 3.2.15 deployments, especially internet-facing systems.
Check official PbootCMS guidance for a patched release or supported mitigation.
Restrict public access where operationally possible until authoritative remediation is available.
Monitor affected servers for unexpected file changes, processes, accounts, and outbound connections.
Preserve relevant web, application, authentication, and system logs for investigation.
Validation and detection
Confirm deployed PbootCMS versions using trusted inventory and installation records.
Determine whether the named controller and helper components are present and publicly reachable.
Review logs for anomalous requests involving the named components.
Verify any vendor-recommended update or mitigation in a controlled environment.
After remediation, confirm external exposure is reduced and monitor for recurrence.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code
Improper Control of Generation of Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.