CVE-2022-44136 is a critical-severity (CVSS 9.8) remote code execution vulnerability in tribalsystems/zenario. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for tribalsystems/zenario — see the affected versions and patch details below.
Zenario CMS is vulnerable to Remote Code Execution (RCE).
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-44136.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
tribalsystems/zenarioReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Zenario CMS 9.3.57186 is vulnerable to Remote Code Excution (RCE).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | tribalsystems/zenario | all versions | 9.0.57473composer require tribalsystems/zenario:^9.0.57473 |
Affected Products
zenariotribalsystemsResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tribalsystems/zenario, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tribalsystems/zenario to 9.0.57473 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-44136 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-44136 in your dependencies?
Find it across Packagist, including transitive dependencies.