Credential disclosure via plaintext job configuration storage
Published Jul 9, 2025 · Updated Nov 4, 2025
Plaintext credential storage in Jenkins ReadyAPI Functional Testing Plugin 1.11 and earlier allows remote authenticated users to read secrets. The plugin writes SLM License Access Keys, client secrets, and passwords directly into affected job config.xml files without encryption. Item/Extended Read permission exposes the files through Jenkins, while controller file-system access exposes the same stored values locally.
Summary
What happened
Plaintext credential storage in Jenkins ReadyAPI Functional Testing Plugin 1.11 and earlier allows remote authenticated users to read secrets. The plugin writes SLM License Access Keys, client secrets, and passwords directly into affected job config.xml files without encryption. Item/Extended Read permission exposes the files through Jenkins, while controller file-system access exposes the same stored values locally.
The record
- CVE
- CVE-2025-53656
- Published
- Jul 9, 2025
- Updated
- Nov 4, 2025
- Vendor
- Jenkins Project
- Product
- ReadyAPI Functional Testing Plugin
- Classifications
- CWE-256, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo