dbcve.org
Monitor Remote JobApplication · Jenkins

CVE-2025-31725

MEDIUM · 5.5 CVSS v3.1 Published 2025-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Jenkins monitor-remote-job Plugin 1.0 stores passwords unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission, or access to the Jenkins controller file system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Jenkins monitor-remote-job Plugin 1.0 stores sensitive passwords in plaintext within job config.xml files on the Jenkins controller. These credentials can be extracted by any user with Extended Read permission on Jenkins jobs or by anyone with filesystem access to the Jenkins controller, leading to credential disclosure.

MitigationIdentify and remove or encrypt stored passwords in job configurations, restrict Extended Read permission to necessary users only, and limit filesystem access to the Jenkins controller. Consider upgrading the plugin if a patched version becomes available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Monitor Remote JobApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify monitor-remote-job plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed, or check the plugins directory on the Jenkins controller for the monitor-remote-job plugin.
    Affected if The monitor-remote-job plugin appears in the installed plugins list.
  2. Confirm the plugin version is 1.0
    In the plugin manager Installed tab, locate the monitor-remote-job plugin and note the Version column. Alternatively, inspect the plugin's manifest file (META-INF/MANIFEST.MF) in the plugin's .jpi or .hpi file.
    Affected if The installed version is exactly 1.0.
  3. Inspect job config.xml files for plaintext passwords
    Locate and examine job config.xml files in JENKINS_HOME/jobs/*/config.xml. Search within these XML files for password fields or sensitive credential values that may be stored in plaintext rather than masked or encrypted.
    Affected if Job config.xml files contain plaintext password strings related to remote job configurations.
  4. Identify users with Extended Read permission
    Review Jenkins authorization settings under Manage Jenkins > Configure Global Security. Check which users or groups are granted Extended Read permission on jobs.
    Affected if Extended Read permission is granted to users beyond administrators, enabling potential extraction of job configuration data.

A user is affected if the monitor-remote-job plugin version 1.0 is installed and job config.xml files contain plaintext passwords that could be accessed via Extended Read permission or filesystem access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Identify and remove or encrypt stored passwords in job configurations, restrict Extended Read permission to necessary users only, and limit filesystem access to the Jenkins controller. Consider upgrading the plugin if a patched version becomes available.

Recommended fix Moderate confidence

Update to the latest version of the monitor-remote-job plugin that contains the security fix (check Jenkins Security Advisory for the specific fixed version number)

  1. 1. Navigate to the Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Select the 'Installed' tab
  4. 4. Locate the 'Monitor Remote Job' plugin
  5. 5. If an update is available, click 'Update' to install the fixed version
  6. 6. Restart Jenkins if required after the update
  7. 7. Verify the plugin has been updated to the secure version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Monitor Remote Job Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31725 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31725 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data