{"api_version":"1","generated_at":"2026-06-23T09:52:05+00:00","cve":"CVE-2015-9276","urls":{"html":"https://cve.report/CVE-2015-9276","api":"https://cve.report/api/cve/CVE-2015-9276.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2015-9276","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2015-9276"},"summary":{"title":"CVE-2015-9276","description":"SmarterTools SmarterMail before 13.3.5535 was vulnerable to stored XSS by bypassing the anti-XSS mechanisms. It was possible to run JavaScript code when a victim user opens or replies to the attacker's email, which contained a malicious payload. Therefore, users' passwords could be reset by using an XSS attack, as the password reset page did not need the current password.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2019-01-16 16:29:00","updated_at":"2019-01-24 21:28:00"},"problem_types":["CWE-79"],"metrics":[],"references":[{"url":"https://www.nccgroup.trust/globalassets/our-research/uk/technical-advisories/2015/technical-advisory-smartermail-stored-xss-in-emails-v2.pdf","name":"https://www.nccgroup.trust/globalassets/our-research/uk/technical-advisories/2015/technical-advisory-smartermail-stored-xss-in-emails-v2.pdf","refsource":"MISC","tags":["Third Party Advisory"],"title":"","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.nccgroup.trust/uk/our-research/smartermail-stored-xss-in-emails/","name":"https://www.nccgroup.trust/uk/our-research/smartermail-stored-xss-in-emails/","refsource":"MISC","tags":["Third Party Advisory"],"title":"SmarterMail - Stored XSS in emails","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.smartertools.com/smartermail/release-notes/13","name":"https://www.smartertools.com/smartermail/release-notes/13","refsource":"MISC","tags":["Release Notes"],"title":"Release Notes and Version History","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2015-9276","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2015-9276","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2015","cve_id":"9276","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"smartertools","cpe5":"smartermail","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2015","cve_id":"9276","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"smartertools","cpe5":"smartermail","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2015-9276","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"SmarterTools SmarterMail before 13.3.5535 was vulnerable to stored XSS by bypassing the anti-XSS mechanisms. It was possible to run JavaScript code when a victim user opens or replies to the attacker's email, which contained a malicious payload. Therefore, users' passwords could be reset by using an XSS attack, as the password reset page did not need the current password."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"name":"https://www.nccgroup.trust/uk/our-research/smartermail-stored-xss-in-emails/","refsource":"MISC","url":"https://www.nccgroup.trust/uk/our-research/smartermail-stored-xss-in-emails/"},{"name":"https://www.nccgroup.trust/globalassets/our-research/uk/technical-advisories/2015/technical-advisory-smartermail-stored-xss-in-emails-v2.pdf","refsource":"MISC","url":"https://www.nccgroup.trust/globalassets/our-research/uk/technical-advisories/2015/technical-advisory-smartermail-stored-xss-in-emails-v2.pdf"},{"name":"https://www.smartertools.com/smartermail/release-notes/13","refsource":"MISC","url":"https://www.smartertools.com/smartermail/release-notes/13"}]}},"nvd":{"publishedDate":"2019-01-16 16:29:00","lastModifiedDate":"2019-01-24 21:28:00","problem_types":["CWE-79"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.0","vectorString":"CVSS:3.0/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:smartertools:smartermail:*:*:*:*:*:*:*:*","versionEndExcluding":"13.3.5535","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2015","CveId":"9276","Ordinal":"144151","Title":"CVE-2015-9276","CVE":"CVE-2015-9276","Year":"2015"},"notes":[{"CveYear":"2015","CveId":"9276","Ordinal":"1","NoteData":"SmarterTools SmarterMail before 13.3.5535 was vulnerable to stored XSS by bypassing the anti-XSS mechanisms. It was possible to run JavaScript code when a victim user opens or replies to the attacker's email, which contained a malicious payload. Therefore, users' passwords could be reset by using an XSS attack, as the password reset page did not need the current password.","Type":"Description","Title":null},{"CveYear":"2015","CveId":"9276","Ordinal":"2","NoteData":"2019-01-16","Type":"Other","Title":"Published"},{"CveYear":"2015","CveId":"9276","Ordinal":"3","NoteData":"2019-01-16","Type":"Other","Title":"Modified"}]}}}