CVE-2008-6831 json
Multiple cross-site scripting (XSS) vulnerabilities in Atlassian JIRA Enterprise Edition 3.13 allow remote attackers to inject arbitrary web script or HTML via the (1) fullname (Full Name) parameter in the ViewProfile page or (2) returnUrl parameter in a form, as demonstrated using secure/AddComment!default.jspa (aka "Add Comment").
published 17y ago modified 5mo ago also EUVD-2008-6791
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
Multiple cross-site scripting (XSS) vulnerabilities in Atlassian JIRA Enterprise Edition 3.13 allow remote attackers to inject arbitrary web script or HTML via the (1) fullname (Full Name) parameter in the ViewProfile page or (2) returnUrl parameter in a form, as demonstrated using secure/AddComment!default.jspa (aka "Add Comment").
Patch / fix
Is CVE-2008-6831 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.26% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
confluence.atlassian.com
/display/JIRA/JIRA+Security+Advisory+2008-10-29
patch, vendor-advisory
-
secunia.com
/advisories/32113
third-party-advisory, vendor-advisory
-
osvdb.org
/49415
vdb-entry
-
securityfocus.com
/bid/31967
vdb-entry
-
osvdb.org
/49416
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/46168
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/46167
vdb-entry
Sources
- CVE List CVE-2008-6831
- NVD CVE-2008-6831
Fencer Intel 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.