CVE-2025-53674: Jenkins Sensedia API Platform Plugin Vulnerability Exposes Unencrypted Tokens

Summary

09/07/2025
No i
Moderate
4.3

CVE-2025-53674: Jenkins Sensedia API Platform Plugin vulnerability exposes unencrypted tokens. Affects org.jenkins-ci.plugins:sensedia-api-platform versions < 1.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Jenkins Sensedia API Platform Plugin is designed to facilitate integration with the Sensedia API Manager, allowing users to manage API interactions within Jenkins. This plugin enhances the capabilities of Jenkins by enabling seamless API management, but it has a critical vulnerability that compromises the security of sensitive tokens used for API integration.

Vulnerability Detail

The vulnerability in the Jenkins Sensedia API Platform Plugin arises from the failure to mask the Sensedia API Manager integration token on the global configuration form. This oversight allows potential attackers to observe and capture the integration token, which could lead to unauthorized access to the API Manager and sensitive data. The vulnerability is classified under CWE-256, indicating improper handling of sensitive information.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, ensure that access to the Jenkins configuration is restricted to trusted users only, minimizing the risk of exposure to unauthorized individuals. Additionally, consider using environment variables to store sensitive tokens instead of hardcoding them in the configuration.

Conclusion

The Jenkins Sensedia API Platform Plugin vulnerability (CVE-2025-53674) poses a significant risk by exposing sensitive integration tokens. Users are advised to update to the latest version to mitigate this risk and ensure the security of their API interactions.

See every vulnerability recorded for org.jenkins-ci.plugins:sensedia-api-platform →

Share this vulnerability

FAQ

The vulnerability allows the Sensedia API Manager integration token to be visible in the global configuration form, posing a risk of unauthorized access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The CVSS score of this vulnerability is 4.3, indicating a moderate severity level.

Yes, a patch is available in version 1.1 of the Jenkins Sensedia API Platform Plugin.

If immediate updates are not possible, restrict access to the Jenkins configuration and consider using environment variables for sensitive tokens.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:sensedia-api-platform.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback