S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Oct 8, 2024

CVE-2022-0666 Scanner

CVE-2022-0666 Scanner - CRLF Injection vulnerability in Microweber

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsurl
CostFree
3.3k
Times Used
continuous scan runs
4.7k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2022-0666
7.5
CVSShigh
Exploitable remotely over the internet · no authentication required · user interaction needed.

CRLF Injection leads to Stack Trace Exposure due to lack of filtering at https://demo.microweber.org/ in Packagist microweber/microweber prior to 1.2.11.

Attack Vector
Network
Privileges Req.
None
User Interaction
Required
Affected
microweber/microweberby microweber
AFFECTED< 1.2.11SAFE ✓≥ 1.2.11
Updated Aug 22, 2026View on NVD →
Detail

Microweber is a popular CMS platform used by small and medium-sized enterprises for web development and content management. It is known for its ease of use and drag-and-drop functionality, which reduces the need for extensive technical knowledge. This software assists businesses in building online presences quickly and efficiently. It supports e-commerce integration, allowing companies to manage online stores. Web developers and designers can utilize Microweber to implement custom-tailored websites according to client needs. The user-friendly interface and affordable pricing make it an attractive option for startups and budget-conscious businesses.

CRLF Injection is a vulnerability where unauthorized actors can manipulate HTTP headers by injecting Carriage Return (CR) and Line Feed (LF) characters. This can lead to unintended header manipulation that may cause security issues such as response splitting. Attackers exploit this by injecting JavaScript or other malicious code into HTTP responses. The vulnerability can also lead to information disclosure where sensitive data might unintentionally be revealed. It is critical for web applications to sanitize input to block CRLF injection attempts. Preventive measures must be taken to enhance security and protect user data from being compromised.

In the context of Microweber, the CRLF Injection vulnerability exists due to insufficient validation in the handling of HTTP headers. The vulnerable endpoint /api/logout is susceptible as it allows input to determine headers like 'Set-Cookie'. This flaw enables attackers to append additional cookies, potentially diverting control flow or stealing user sessions. Use of %0d%0a characters grants attackers the capability to inject additional headers, modifying server responses. Despite limitations in altering server responses, potential impacts along exploiting sensitive operations and complexes exist. Researchers have advised strengthening input validation and cautioned against including unsanitized user inputs in headers.

Exploitation of the CRLF Injection vulnerability can cause a wide array of harmful effects. Attackers may achieve cookie stealing by redeploying server-authentication cookies, putting user accounts at risk. This may lead to session hijacking or continuation of unauthorized activities under a valid user session. Moreover, attackers could manipulate logs, make genuine activities harder to detect by inserting misleading data, complicating security audits. DNS data can also be altered, redirecting users to malicious sites without their knowledge. Additionally, sensitive information such as internal IP addresses could be mistakenly revealed. Lastly, response Splitting to induce cross-site scripting is feasible, thereby heightening security threats to users.

REFERENCES

Solution Advice
  • Update Microweber to the latest version to patch known vulnerabilities.
  • Implement input validation to ensure special characters are filtered out before processing HTTP request headers.
  • Employ security measures like Content Security Policy (CSP) to prevent the execution of untrusted scripts.
  • Regularly review and audit web application logs to detect suspicious activity early.
  • Educate development teams on secure coding practices to prevent similar vulnerabilities in the future.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.