CVE-2019-15515 : Discourse 2.3.2 sends the CSRF token in the query string.

Discourse 2.3.2 sends the CSRF token in the query string.

Published 2019-08-26 18:15:12

Updated 2019-08-29 20:20:33

Source MITRE

View at NVD, CVE.org

Vulnerability category: Cross-site request forgery (CSRF)

Products affected by CVE-2019-15515

Discourse » Discourse » Version: 2.3.2
cpe:2.3:a:discourse:discourse:2.3.2:*:*:*:*:*:*:*
Matching versions

EPSS FAQ

0.14%

Probability of exploitation activity in the next 30 days EPSS Score History

~ 31 %

Percentile, the proportion of vulnerabilities that are scored at or less

Base Score	Base Severity	CVSS Vector	Exploitability Score	Impact Score	Score Source
4.3	MEDIUM	AV:N/AC:M/Au:N/C:P/I:N/A:N	8.6	2.9	NIST
Access Vector: Network Access Complexity: Medium Authentication: None Confidentiality Impact: Partial Integrity Impact: None Availability Impact: None
6.5	MEDIUM	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N	2.8	3.6	NIST
Attack Vector: Network Attack Complexity: Low Privileges Required: None User Interaction: Required Scope: Unchanged Confidentiality: High Integrity: None Availability: None

CWE-352 Cross-Site Request Forgery (CSRF)

The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.

Assigned by: nvd@nist.gov (Primary)

https://github.com/discourse/discourse/pull/8026

SECURITY: Don't send CSRF token in query string by danielwaterworth · Pull Request #8026 · discourse/discourse · GitHub
Patch;Third Party Advisory

Jump to