CVE-2025-64147: Medium severity Jenkins Curseforge Publisher Plugin vulnerability
Jenkins Curseforge Publisher Plugin 1.0 and earlier stores API Keys unencrypted in job config.xml files on the Jenkins controller as part of its configuration.
These keys can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.
Additionally, the job configuration form does not mask these keys, increasing the potential for attackers to observe and capture them.
As of publication of this advisory, there is no fix.
Other sources
Jenkins Curseforge Publisher Plugin 1.0 does not mask API Keys displayed on the job configuration form, increasing the potential for attackers to observe and capture them.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-64147?
CVE-2025-64147 has been classified with a high severity due to the exposure of API Keys in job configurations.
How do I fix CVE-2025-64147?
To fix CVE-2025-64147, update the Jenkins Curseforge Publisher Plugin to the latest version where the API Key masking issue has been resolved.
What are the risks associated with CVE-2025-64147?
The risks of CVE-2025-64147 include unauthorized access to sensitive data and potential exploitation of API Keys by attackers.
Which versions of the Jenkins Curseforge Publisher Plugin are affected by CVE-2025-64147?
CVE-2025-64147 affects version 1.0 of the Jenkins Curseforge Publisher Plugin.
Is there a workaround for CVE-2025-64147 if I cannot update immediately?
As a temporary measure, you may limit access to the job configuration page to trusted users while planning the update for CVE-2025-64147.