{"api_version":"1","generated_at":"2026-07-23T13:46:31+00:00","cve":"CVE-2022-31127","urls":{"html":"https://cve.report/CVE-2022-31127","api":"https://cve.report/api/cve/CVE-2022-31127.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2022-31127","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2022-31127"},"summary":{"title":"CVE-2022-31127","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.","state":"PUBLIC","assigner":"security-advisories@github.com","published_at":"2022-07-06 18:15:00","updated_at":"2022-07-14 14:31:00"},"problem_types":["CWE-79"],"metrics":[],"references":[{"url":"https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pgjx-7f9g-9463","name":"https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pgjx-7f9g-9463","refsource":"CONFIRM","tags":[],"title":"Improper handling of email input · Advisory · nextauthjs/next-auth · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://next-auth.js.org/providers/email#customizing-emails","name":"https://next-auth.js.org/providers/email#customizing-emails","refsource":"MISC","tags":[],"title":"Email | NextAuth.js","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/nextauthjs/next-auth/commit/ae834f1e08a4a9915665eecb9479c74c6b039c9c","name":"https://github.com/nextauthjs/next-auth/commit/ae834f1e08a4a9915665eecb9479c74c6b039c9c","refsource":"MISC","tags":[],"title":"feat(providers): allow styling e-mail through `theme` option (#4841) · nextauthjs/next-auth@ae834f1 · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://next-auth.js.org/getting-started/upgrade-v4","name":"https://next-auth.js.org/getting-started/upgrade-v4","refsource":"MISC","tags":[],"title":"Upgrade Guide (v4) | NextAuth.js","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/nextauthjs/next-auth/releases/tag/next-auth%40v4.9.0","name":"https://github.com/nextauthjs/next-auth/releases/tag/next-auth%40v4.9.0","refsource":"MISC","tags":[],"title":"Release next-auth@v4.9.0 · nextauthjs/next-auth · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-31127","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-31127","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2022","cve_id":"31127","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"nextauth.js","cpe5":"next-auth","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"node.js","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"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"}},"nvd":{"publishedDate":"2022-07-06 18:15:00","lastModifiedDate":"2022-07-14 14:31:00","problem_types":["CWE-79"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"REQUIRED","scope":"CHANGED","confidentialityImpact":"LOW","integrityImpact":"LOW","availabilityImpact":"NONE","baseScore":6.1,"baseSeverity":"MEDIUM"},"exploitabilityScore":2.8,"impactScore":2.7},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:M/Au:N/C:N/I:P/A:N","accessVector":"NETWORK","accessComplexity":"MEDIUM","authentication":"NONE","confidentialityImpact":"NONE","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":4.3},"severity":"MEDIUM","exploitabilityScore":8.6,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":true}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:nextauth.js:next-auth:*:*:*:*:*:node.js:*:*","versionStartIncluding":"4.0.0","versionEndExcluding":"4.9.0","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:nextauth.js:next-auth:*:*:*:*:*:node.js:*:*","versionEndExcluding":"3.29.8","cpe_name":[]}]}]}},"legacy_mitre":{"record":null,"notes":[]}}}