Discourse-Jira could make SSRF attack by setting Jira URL to an arbitrary location

published 2023-10-06 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-48733

cvss: 4.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits: 0; none known

Discourse-jira is a Discourse plugin allows Jira projects, issue types, fields and field options will be synced automatically. An administrator user can make an SSRF attack by setting the Jira URL to an arbitrary location and enabling the `discourse_jira_verbose_log` site setting. A moderator user could manipulate the request path to the Jira API, allowing them to perform arbitrary GET requests using the Jira API credentials, potentially with elevated permissions, used by the application.

Patch / fix

links 2

github.com/discourse/discourse-jira@8a2d3ad commit
github.com/discourse/discourse-jira#50 pull request

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2 y ago (2024-09-19)

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.1	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N
NVD	3.1	4.1	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N

Affected products

discourse discourse-jira

Classification

Weakness

CWE-691 Insufficient Control Flow Management
CWE-918 Server-Side Request Forgery

References

Sources

CVE List CVE-2023-44384
NVD CVE-2023-44384

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary