{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15515 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15515 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15515 is a medium-severity vulnerability in Discourse Discourse, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-15515 and fix it if it is affected.\n\nWhat it is: CVE-2019-15515 is a medium-severity vulnerability in Discourse Discourse, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-15515 in the wild and no public exploit code.\n\nAffected product: Discourse Discourse. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-15515/ (Markdown: https://insights.sbomify.com/CVE-2019-15515/index.md)","id":"CVE-2019-15515","markdown":"https://insights.sbomify.com/CVE-2019-15515/index.md","name":"CVE-2019-15515","record":{"aliases":["GHSA-p36h-rrm6-fjjp"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Discourse forum","requires_auth":"none","summary":"Discourse exposes CSRF tokens in query strings, allowing attackers to bypass CSRF protections and perform unauthorized actions on behalf of users.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"discourse","vendor":"discourse"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Discourse 2.3.2 sends the CSRF token in the query string.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-15515","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"discourse:discourse","products":["discourse:discourse"],"type":"csrf","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2019-15516"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-15514"},"products":["n/a"],"published":"2019-08-26","related":[{"cvss_score":10,"headline":"RCE via malicious SNS subscription payload","id":"CVE-2021-41163","kev_date_added":null,"published":"2021-10-20"},{"cvss_score":9.1,"headline":"Discourse vulnerable to RCE via admins uploading maliciously zipped file","id":"CVE-2022-36066","kev_date_added":null,"published":"2022-09-29"},{"cvss_score":8.9,"headline":"Discourse user account takeover via email and invite link","id":"CVE-2022-39356","kev_date_added":null,"published":"2022-11-02"},{"cvss_score":8.8,"headline":"Discourse vulnerable to Cross-site Scripting in local oneboxes","id":"CVE-2023-22468","kev_date_added":null,"published":"2023-01-26"},{"cvss_score":8.7,"headline":"Discourse leaks private topic title and post excerpt via user action API endpoint","id":"CVE-2026-27934","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":8.7,"headline":"Discourse vulnerable to DoS via large URL payload in PM to a bot","id":"CVE-2025-48053","kev_date_added":null,"published":"2025-06-09"},{"cvss_score":8.6,"headline":"Discourse vulnerable to unlimited mentioned users in message serializer","id":"CVE-2023-48297","kev_date_added":null,"published":"2024-01-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Discourse exposes CSRF tokens in query strings, allowing attackers to bypass CSRF protections and perform unauthorized actions on behalf of users.","url":"https://insights.sbomify.com/CVE-2019-15515/"}