CVE-2021-47964: Schlix CMS 2.2.6-6 Remote Code Execution via core.blockmanager
Schlix CMS 2.2.6-6 contains a remote code execution vulnerability that allows authenticated attackers to execute arbitrary PHP code by uploading malicious extension packages through the block manager. Attackers can upload a crafted ZIP file containing PHP code in the packageinfo.inc file and trigger execution by accessing the About tab of the installed extension.
Security readout for executives and security teams
Plain-English summary
Schlix CMS 2.2.6-6 has a high-severity flaw that can let a logged-in attacker run PHP code on the server through the extension/block manager workflow. This can lead to full compromise of the website and underlying application data.
Executive priority
High priority for any organization using Schlix CMS 2.2.6-6. The main business risk is server-side code execution after account compromise or misuse. Prioritize inventory, access restriction, monitoring, and vendor guidance review.
Technical view
CVE-2021-47964 is CWE-94 code injection in Schlix CMS 2.2.6-6. Sources describe authenticated remote code execution through uploaded extension packages handled by core.blockmanager, with execution triggered through the installed extension interface. CVSS 3.1 is 8.8: network exploitable, low privileges, no user interaction.
Likely exposure
Exposure is likely limited to organizations running Schlix CMS 2.2.6-6 where authenticated users can access extension or block manager functionality. Public internet exposure increases business risk, but the vulnerability still requires a valid account or compromised credentials.
Exploitation context
A public ExploitDB reference exists, so technical details are publicly available. The source bundle does not indicate CISA KEV listing or confirmed active exploitation. Treat this as credible and actionable, but do not assume active exploitation without additional evidence.
Researcher notes
Evidence is strongest for the affected version and attack class. The sources do not name a patch, fixed version, or active exploitation. Validation should focus on version confirmation, privileged CMS access paths, suspicious extension artifacts, and log anomalies.
Mitigation direction
Check Schlix and advisory sources for vendor remediation or fixed releases.
Restrict CMS administration to trusted networks and named accounts.
Remove unnecessary accounts with extension or block manager access.
Disable extension package uploads if operationally possible.
Review suspicious extensions before returning affected sites to normal operation.
Validation and detection
Inventory Schlix CMS instances and confirm exact versions.
Identify systems running Schlix CMS 2.2.6-6.
Review who can access extension or block manager features.
Inspect recently installed extensions for unauthorized changes.
Review web and CMS logs for unusual extension-management activity.
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.
2CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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 ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.