CVE-2025-31725 — monitor-remote-job
MEDIUMCVE-2025-31725 is a medium-severity (CVSS 4.3) CWE-284 vulnerability in org.ukiuni.monitor-remote-job-plugin:monitor-remote-job. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Jenkins monitor-remote-job Plugin Stores Passwords Unencrypted
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-31725.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.ukiuni.monitor-remote-job-plugin:monitor-remote-jobReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins monitor-remote-job Plugin 1.0 stores passwords unencrypted in job config.xml files on the Jenkins controller as part of its configuration.
These passwords can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.
As of publication of this advisory, there is no fix.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.ukiuni.monitor-remote-job-plugin:monitor-remote-job | all versions | No fix |
Affected Products
monitor-remote-jobjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.ukiuni.monitor-remote-job-plugin:monitor-remote-job, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.ukiuni.monitor-remote-job-plugin:monitor-remote-job for CVE-2025-31725. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2025-31725 in your dependencies?
Find it across Maven, including transitive dependencies.