CVE-2024-52552 json
Stored XSS vulnerability in Jenkins Authorize Project Plugin
published last yr. modified 4mo ago also GHSA-8886-8v27-85j8 , EUVD-2024-3219
- cvss
- 8.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
Jenkins Authorize Project Plugin 1.7.2 and earlier evaluates a string containing the job name with JavaScript on the Authorization view, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
Patch / fix
- maven org.jenkins-ci.plugins:authorize-project 1.8.0
Is CVE-2024-52552 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.0 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:authorize-project | <1.8.0 |
1.8.0 |
Affected products
- Jenkins Project Jenkins Authorize Project Plugin
- jenkins_project jenkins_authorize_project_plugin
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
jenkins.io
/security/advisory/2024-11-13/#SECURITY-3010
vendor-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2024-52552
advisory
-
github.com
/jenkinsci/authorize-project-plugin
package
Sources
- CVE List CVE-2024-52552
- GitHub Advisory GHSA-8886-8v27-85j8
- NVD CVE-2024-52552
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.