CVE-2013-7370: methodOverride Middleware Reflected Cross-Site Scripting in connect

connect Updated 02 Oct 2025

Summary

31/08/2020
Yes i
Low
Not published

CVE-2013-7370: methodOverride Middleware Reflected Cross-Site Scripting in connect. Affects connect versions < 2.8.1. Fixed in 2.8.1. How to fix ↓

Also tracked for

The same CVE-2013-7370 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Connect is a stack of middleware that is executed in order in each request. The "methodOverride" middleware allows the HTTP POST to override the method of the request with the value of the "_method" post key or with the header "x-http-method-override". This vulnerability arises due to the lack of input validation on the user post input, allowing the req.method to contain any value. As a result, when the req.method does not match any common method VERB, Connect responds with a 404 page containing the unencoded method value, leading to a reflected cross-site scripting (XSS) vulnerability.

Vulnerability Detail

The vulnerability allows an attacker to inject malicious scripts into the 404 error page, which can be executed by unsuspecting users visiting the page. This can lead to various consequences, such as stealing sensitive information, performing actions on behalf of the user, or spreading malware. The vulnerability has a low severity rating (CWE-79) and affects Connect versions <= 2.8.0.

How To Fix

Latest published version: 3.7.0 as of 23 Oct 2026

npm install connect@3.7.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.8.1

This is the first release that contains the fix.

npm install connect@2.8.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If updating or disabling the middleware is not feasible, you can implement input validation on the user post input to ensure that only valid HTTP methods are accepted. This can be done by checking the value of req.method against a whitelist of allowed methods before processing the request.

Conclusion

The methodOverride middleware in Connect versions <= 2.8.0 is vulnerable to reflected cross-site scripting (XSS) attacks. To protect your application, it is recommended to update to the latest version of Connect or disable the middleware if not needed. Implementing input validation on user post input can also help mitigate the vulnerability. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for connect →

Share this vulnerability

FAQ

Connect is a stack of middleware for Node.js that provides a modular way to handle HTTP requests and responses.

The methodOverride middleware allows HTTP POST requests to override the method of the request using the "_method" post key or the "x-http-method-override" header.

The vulnerability occurs because the user post input is not properly validated, allowing the req.method value to be any arbitrary string. When the req.method does not match any common method VERB, Connect responds with a 404 error page containing the unencoded method value, leading to a reflected cross-site scripting vulnerability.

The vulnerability allows an attacker to inject malicious scripts into the 404 error page, which can be executed by unsuspecting users visiting the page. This can lead to various consequences, such as stealing sensitive information, performing actions on behalf of the user, or spreading malware.

You can mitigate this vulnerability by updating to the newest version of Connect (2.8.1 or later) or by disabling the methodOverride middleware if it is not required for your application. Additionally, implementing input validation on the user post input can help prevent the vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for connect.

How To Fix

Latest published version: 3.7.0 as of 23 Oct 2026

npm install connect@3.7.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.8.1

This is the first release that contains the fix.

npm install connect@2.8.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback