Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-0557 is a high-severity OS Command Injection (CWE-78) vulnerability in Microweber Microweber. Its CVSS base score is 7.2 (High).
Operationally, ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2022-0557 is an OS command injection vulnerability, tracked under CWE-78, that affects the microweber/microweber package on Packagist in all versions prior to 1.2.11. The flaw received a CVSS 3.1 score of 7.2 and permits an attacker to execute arbitrary operating-system commands through the application.
An authenticated user with high privileges can exploit the issue over the network without user interaction. Successful exploitation grants the attacker full control over confidentiality, integrity, and availability of the affected system, enabling remote code execution and potential full host compromise.
Public references point to a specific commit that resolves the injection flaw, and the project released version 1.2.11 to address it. Security advisories and the associated huntr.dev report therefore recommend upgrading to the patched release as the primary mitigation.
Public proof-of-concept exploits have been published on Exploit-DB and PacketStorm, yet the EPSS score has remained flat at 0.1686 with no material increase after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-1209
Vulnerability Data
OS Command Injection in Packagist microweber/microweber prior to 1.2.11.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires applying the vendor patch (v1.2.11) that eliminates the OS command injection flaw.
Mandates input validation/sanitization on untrusted data to block the arbitrary command execution path.
Limits the high-privilege accounts that can reach the vulnerable code path, reducing exploitability.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.
Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.