dbcve.org
Readyapi Functional TestingApplication · Jenkins

CVE-2025-53656

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-09
Fix available
A fix is available. Upgrade to after 1.11 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 ReadyAPI Functional Testing Plugin 1.11 and earlier stores SLM License Access Keys, client secrets, and passwords unencrypted in job config.xml files on the Jenkins controller, where they can be viewed by users with Item/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 ReadyAPI Functional Testing Plugin versions 1.11 and earlier stores SLM License Access Keys, client secrets, and passwords in plaintext within job config.xml files. These credentials are accessible to users with Item/Extended Read permission or anyone with filesystem access to the Jenkins controller, exposing sensitive authentication material.

MitigationUpgrade to a patched version of the ReadyAPI Functional Testing Plugin once available, rotate all exposed credentials (SLM License keys, client secrets, passwords), and review user permissions to limit Item/Extended Read access to authorized personnel only.

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
Readyapi Functional TestingApplication
Affected:<= 1.11

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify if ReadyAPI Functional Testing Plugin is installed
    Navigate to Jenkins Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins
    Affected if The ReadyAPI Functional Testing Plugin appears in the installed plugins list
  2. Check the plugin version
    In Manage Plugins > Installed, find the ReadyAPI Functional Testing entry and note the Version column. Or inspect the manifest in the plugin WAR file: WEB-INF/plugins/ready-api-functional-testing-plugin.jpi
    Affected if The installed version is 1.11 or earlier
  3. Identify jobs using the plugin
    Search job config.xml files for the presence of the ReadyAPI Functional Testing builder: grep -r 'ReadyApiFunctionalTesting' $JENKINS_HOME/jobs/*/config.xml
    Affected if Any job config.xml contains ReadyAPI Functional Testing configuration
  4. Inspect job config.xml for plaintext credentials
    Examine the config.xml files of jobs using the plugin for plaintext strings matching SLM License Access Keys, client secrets, or passwords. Look for <slmLicenseKey>, <clientSecret>, or <password> elements with unmasked values
    Affected if Credentials appear in plaintext rather than masked or encrypted
  5. Verify filesystem access to config.xml files
    Check file permissions on $JENKINS_HOME/jobs/*/config.xml. Any user or process with read access to these files can retrieve the plaintext credentials
    Affected if Filesystem permissions allow unauthorized read access to job config.xml files

You are affected if the ReadyAPI Functional Testing Plugin version 1.11 or earlier is installed AND any job configuration contains plaintext credentials that can be read by users with Item/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
Upgrade available Upgrade to a release after 1.11
Interim mitigation

Upgrade to a patched version of the ReadyAPI Functional Testing Plugin once available, rotate all exposed credentials (SLM License keys, client secrets, passwords), and review user permissions to limit Item/Extended Read access to authorized personnel only.

Recommended fix High confidence

1.12

  1. Navigate to Jenkins Manage Plugins page
  2. Select the 'Installed' tab
  3. Locate the ReadyAPI Functional Testing plugin
  4. If an update is available, click 'Update' to upgrade to version 1.12 or later
  5. Restart Jenkins if required to complete the update
  6. Verify the plugin is updated to version 1.12 or newer

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

Fix this in Readyapi Functional Testing Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53656 — 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-53656 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