Integration-token exposure via unmasked configuration field
Published Jul 9, 2025 · Updated Nov 4, 2025
Credential exposure in Jenkins Sensedia Api Platform tools Plugin 1.0 allows remote attackers to capture an integration token. The global configuration form renders the stored Sensedia API Manager integration token without masking it as a secret field. Exposure requires the configured token to be present on the opened controller configuration page and reveals that token without reported integrity or availability impact.
Summary
What happened
Credential exposure in Jenkins Sensedia Api Platform tools Plugin 1.0 allows remote attackers to capture an integration token. The global configuration form renders the stored Sensedia API Manager integration token without masking it as a secret field. Exposure requires the configured token to be present on the opened controller configuration page and reveals that token without reported integrity or availability impact.
The record
- CVE
- CVE-2025-53674
- Published
- Jul 9, 2025
- Updated
- Nov 4, 2025
- Vendor
- Jenkins Project
- Product
- Sensedia Api Platform tools
- Classifications
- CWE-256, T1552
- Attack vector
- network
- Privileges
- unauthenticated
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=1.0
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.
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