{"id":"CVE-2022-31127","state":"PUBLISHED","title":"Improper handling of email input in next-auth","description":"NextAuth.js is a complete open source authentication solution for Next.js applications. An attacker can pass a compromised input to the e-mail [signin endpoint](https://next-auth.js.org/getting-started/rest-api#post-apiauthsigninprovider) that contains some malicious HTML, tricking the e-mail server to send it to the user, so they can perform a phishing attack. Eg.: `balazs@email.com, <a href=\"http://attacker.com\">Before signing in, claim your money!</a>`. This was previously sent to `balazs@email.com`, and the content of the email containing a link to the attacker's site was rendered in the HTML. This has been remedied in the following releases, by simply not rendering that e-mail in the HTML, since it should be obvious to the receiver what e-mail they used: next-auth v3 users before version 3.29.8 are impacted. (We recommend upgrading to v4, as v3 is considered unmaintained. next-auth v4 users before version 4.9.0 are impacted. If for some reason you cannot upgrade, the workaround requires you to sanitize the `email` parameter that is passed to `sendVerificationRequest` and rendered in the HTML. If you haven't created a custom `sendVerificationRequest`, you only need to upgrade. Otherwise, make sure to either exclude `email` from the HTML body or efficiently sanitize it.","publishedAt":"2022-07-06T18:00:16.000Z","updatedAt":"2025-04-22T17:51:28.600Z","severity":{"score":7.1,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L","source":"GitHub_M"},"assigner":"GitHub_M","products":["nextauthjs next-auth"],"affected":[{"vendor":"nextauthjs","product":"next-auth","versions":[{"version":"< 3.29.8","status":"affected"},{"version":">= 4.0.0, < 4.9.0","status":"affected"}]}],"references":["https://next-auth.js.org/getting-started/upgrade-v4","https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pgjx-7f9g-9463","https://github.com/nextauthjs/next-auth/commit/ae834f1e08a4a9915665eecb9479c74c6b039c9c","https://github.com/nextauthjs/next-auth/releases/tag/next-auth%40v4.9.0","https://next-auth.js.org/providers/email#customizing-emails"],"weaknesses":["CWE-79"],"ingestedAt":"2026-10-29T19:50:06.617Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2022/31xxx/CVE-2022-31127.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.1","cveMetadata":{"cveId":"CVE-2022-31127","state":"PUBLISHED","datePublished":"2022-07-06T18:00:16.000Z","dateUpdated":"2025-04-22T17:51:28.600Z","assignerShortName":"GitHub_M","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","dateReserved":"2022-05-18T00:00:00.000Z"},"containers":{"cna":{"title":"Improper handling of email input in next-auth","descriptions":[{"lang":"en","value":"NextAuth.js is a complete open source authentication solution for Next.js applications. An attacker can pass a compromised input to the e-mail [signin endpoint](https://next-auth.js.org/getting-started/rest-api#post-apiauthsigninprovider) that contains some malicious HTML, tricking the e-mail server to send it to the user, so they can perform a phishing attack. Eg.: `balazs@email.com, <a href=\"http://attacker.com\">Before signing in, claim your money!</a>`. This was previously sent to `balazs@email.com`, and the content of the email containing a link to the attacker's site was rendered in the HTML. This has been remedied in the following releases, by simply not rendering that e-mail in the HTML, since it should be obvious to the receiver what e-mail they used: next-auth v3 users before version 3.29.8 are impacted. (We recommend upgrading to v4, as v3 is considered unmaintained. next-auth v4 users before version 4.9.0 are impacted. If for some reason you cannot upgrade, the workaround requires you to sanitize the `email` parameter that is passed to `sendVerificationRequest` and rendered in the HTML. If you haven't created a custom `sendVerificationRequest`, you only need to upgrade. Otherwise, make sure to either exclude `email` from the HTML body or efficiently sanitize it."}],"affected":[{"vendor":"nextauthjs","product":"next-auth","versions":[{"version":"< 3.29.8","status":"affected"},{"version":">= 4.0.0, < 4.9.0","status":"affected"}]}],"references":[{"url":"https://next-auth.js.org/getting-started/upgrade-v4","tags":["x_refsource_MISC"]},{"url":"https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pgjx-7f9g-9463","tags":["x_refsource_CONFIRM"]},{"url":"https://github.com/nextauthjs/next-auth/commit/ae834f1e08a4a9915665eecb9479c74c6b039c9c","tags":["x_refsource_MISC"]},{"url":"https://github.com/nextauthjs/next-auth/releases/tag/next-auth%40v4.9.0","tags":["x_refsource_MISC"]},{"url":"https://next-auth.js.org/providers/email#customizing-emails","tags":["x_refsource_MISC"]}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":7.1,"baseSeverity":"HIGH","confidentialityImpact":"LOW","integrityImpact":"LOW","privilegesRequired":"NONE","scope":"CHANGED","userInteraction":"REQUIRED","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-79","description":"CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')","lang":"en","type":"CWE"}]}],"providerMetadata":{"shortName":"GitHub_M","dateUpdated":"2022-07-06T18:00:16.000Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa"},"source":{"advisory":"GHSA-pgjx-7f9g-9463","discovery":"UNKNOWN"},"x_legacyV4Record":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2022-31127","STATE":"PUBLIC","TITLE":"Improper handling of email input in next-auth"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"next-auth","version":{"version_data":[{"version_value":"< 3.29.8"},{"version_value":">= 4.0.0, < 4.9.0"}]}}]},"vendor_name":"nextauthjs"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"NextAuth.js is a complete open source authentication solution for Next.js applications. An attacker can pass a compromised input to the e-mail [signin endpoint](https://next-auth.js.org/getting-started/rest-api#post-apiauthsigninprovider) that contains some malicious HTML, tricking the e-mail server to send it to the user, so they can perform a phishing attack. Eg.: `balazs@email.com, <a href=\"http://attacker.com\">Before signing in, claim your money!</a>`. This was previously sent to `balazs@email.com`, and the content of the email containing a link to the attacker's site was rendered in the HTML. This has been remedied in the following releases, by simply not rendering that e-mail in the HTML, since it should be obvious to the receiver what e-mail they used: next-auth v3 users before version 3.29.8 are impacted. (We recommend upgrading to v4, as v3 is considered unmaintained. next-auth v4 users before version 4.9.0 are impacted. If for some reason you cannot upgrade, the workaround requires you to sanitize the `email` parameter that is passed to `sendVerificationRequest` and rendered in the HTML. If you haven't created a custom `sendVerificationRequest`, you only need to upgrade. Otherwise, make sure to either exclude `email` from the HTML body or efficiently sanitize it."}]},"impact":{"cvss":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":7.1,"baseSeverity":"HIGH","confidentialityImpact":"LOW","integrityImpact":"LOW","privilegesRequired":"NONE","scope":"CHANGED","userInteraction":"REQUIRED","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')"}]}]},"references":{"reference_data":[{"name":"https://next-auth.js.org/getting-started/upgrade-v4","refsource":"MISC","url":"https://next-auth.js.org/getting-started/upgrade-v4"},{"name":"https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pgjx-7f9g-9463","refsource":"CONFIRM","url":"https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pgjx-7f9g-9463"},{"name":"https://github.com/nextauthjs/next-auth/commit/ae834f1e08a4a9915665eecb9479c74c6b039c9c","refsource":"MISC","url":"https://github.com/nextauthjs/next-auth/commit/ae834f1e08a4a9915665eecb9479c74c6b039c9c"},{"name":"https://github.com/nextauthjs/next-auth/releases/tag/next-auth%40v4.9.0","refsource":"MISC","url":"https://github.com/nextauthjs/next-auth/releases/tag/next-auth%40v4.9.0"},{"name":"https://next-auth.js.org/providers/email#customizing-emails","refsource":"MISC","url":"https://next-auth.js.org/providers/email#customizing-emails"}]},"source":{"advisory":"GHSA-pgjx-7f9g-9463","discovery":"UNKNOWN"}}},"adp":[{"title":"CVE Program Container","references":[{"url":"https://next-auth.js.org/getting-started/upgrade-v4","tags":["x_refsource_MISC","x_transferred"]},{"url":"https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pgjx-7f9g-9463","tags":["x_refsource_CONFIRM","x_transferred"]},{"url":"https://github.com/nextauthjs/next-auth/commit/ae834f1e08a4a9915665eecb9479c74c6b039c9c","tags":["x_refsource_MISC","x_transferred"]},{"url":"https://github.com/nextauthjs/next-auth/releases/tag/next-auth%40v4.9.0","tags":["x_refsource_MISC","x_transferred"]},{"url":"https://next-auth.js.org/providers/email#customizing-emails","tags":["x_refsource_MISC","x_transferred"]}],"providerMetadata":{"shortName":"CVE","orgId":"af854a3a-2127-422b-91ae-364da2661108","dateUpdated":"2024-08-03T07:11:39.115Z"}},{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2025-04-22T15:45:38.302117Z","id":"CVE-2022-31127","options":[{"Exploitation":"poc"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2025-04-22T17:51:28.600Z"}}]}}}