CVE-2022-3245: microweber/microweber · Code Injection
Affects microweber/microweberSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 20 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
European organizations should implement several specific mitigation strategies beyond generic advice: 1) Conduct a thorough audit of all user input points in the Microweber CMS, especially those accessible to authenticated users, to identify where HTML injection could occur. 2) Apply strict input validation and output encoding to sanitize all user-supplied content before rendering it on web pages, using established libraries or frameworks that handle HTML escaping robustly. 3) Restrict the number of users with high privileges to the minimum necessary and enforce the principle of least privilege to reduce the attack surface. 4) Monitor web application logs for unusual content changes or defacement attempts and implement alerting mechanisms for suspicious activities. 5) If possible, isolate the CMS environment and apply web application firewalls (WAFs) configured to detect and block injection attempts targeting Microweber-specific patterns. 6) Stay informed about updates from the Microweber project and apply patches promptly once available. 7) Educate content managers and administrators about the risks of injecting untrusted content and enforce strict content submission policies.
Description
HTML injection attack is closely related to Cross-site Scripting (XSS). HTML injection uses HTML to deface the page. XSS, as the name implies, injects JavaScript into the page. Both attacks exploit insufficient validation of user input.