CVE-2022-0921
Published: 11 March 2022
Summary
CVE-2022-0921 is a medium-severity Code Injection (CWE-94) vulnerability in Microweber Microweber. Its CVSS base score is 6.7 (Medium).
Operationally, ranked in the top 10.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
CVE-2022-0921 affects the Microweber content management system in versions prior to 1.2.12. The flaw stems from insufficient validation in the Backup/Restore feature, allowing improper control of code generation and unrestricted upload of dangerous file types as classified under CWE-94 and CWE-434. Successful exploitation yields remote code execution with high impact on confidentiality, integrity, and availability.
An attacker with high privileges and local access can abuse the backup and restore functionality to upload and execute arbitrary code on the server without user interaction. This grants the ability to fully compromise the affected installation, including reading, modifying, or deleting data and disrupting service operations.
Public references point to a fix merged in commit 867bdda1b4660b0795ad7f87ab5abe9e44b2b318 on the Microweber repository, which resolves the issue in release 1.2.12; the associated huntr.dev report confirms the patch addresses the backup/restore abuse path.
EPSS scores for the vulnerability rose from a low baseline to a peak of 0.0609 on 2025-12-11 before receding to the current value of 0.0456, indicating a measurable increase in exploitation interest after initial disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-1453
Vulnerability details
Abusing Backup/Restore feature to achieve Remote Code Execution in GitHub repository microweber/microweber prior to 1.2.12.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Dangerous file uploads can be detonated in the chamber to determine malice before any production write or execution occurs.
Requiring identifiable owners for portable devices reduces the attack surface for unrestricted uploads of dangerous file types via anonymous media.
Makes persistent code injection into loaded programs impossible when the executable image itself resides on hardware-protected read-only media.
Prevents unrestricted writing of arbitrary or malicious firmware by keeping hardware write-protect enabled except under tightly controlled manual procedures.
Validates inputs used in dynamic code generation to block injected directives.
Directly prevents execution of attacker-supplied code written into data memory regions.
Scans files from external sources on download/open/execute, blocking unrestricted uploads of dangerous file types.