CVE-2025-53661: Jenkins Testsigma Test Plan Plugin API Key Exposure Vulnerability

io.jenkins.plugins:testsigma Updated 02 Oct 2025

Summary

09/07/2025
No i
Low
3.1

CVE-2025-53661: Jenkins Testsigma Test Plan vulnerability exposes API keys via job configuration form. Affects io.jenkins.plugins:testsigma versions < 1.6. 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 Testsigma Test Plan run Plugin is designed to facilitate the integration of Testsigma with Jenkins, allowing users to run Testsigma test plans directly from their Jenkins environment. This plugin enhances the CI/CD pipeline by enabling automated testing and reporting. However, it has been found to store sensitive API keys in job configuration files, which poses a security risk.

Vulnerability Detail

The vulnerability arises from the way the Testsigma Test Plan run Plugin handles API keys. In versions 1.6 and earlier, these keys are stored in the job 'config.xml' files on the Jenkins controller. Although the keys are encrypted on disk, they are not masked in the job configuration form, making them visible to users with access to the Jenkins interface. This exposure increases the risk of unauthorized access and potential exploitation by attackers who can observe and capture these keys.

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

Currently, there are no specific workarounds mentioned for this vulnerability. However, it is advisable to limit access to the Jenkins interface and ensure that only trusted users have permission to view job configurations.

Conclusion

The Jenkins Testsigma Test Plan run Plugin has a vulnerability that exposes API keys in job configuration files, posing a security risk. Users are advised to monitor for updates and restrict access to mitigate potential threats. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.

See every vulnerability recorded for io.jenkins.plugins:testsigma →

Share this vulnerability

FAQ

CVE-2025-53661 is a vulnerability in the Jenkins Testsigma Test Plan run Plugin that exposes API keys in job configuration files.

The main risk is that unauthorized users could access sensitive API keys, potentially leading to unauthorized access to Testsigma services.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability.

As of now, there is no patch available for this vulnerability. Users should keep an eye on the plugin repository for future updates.

If you cannot update the plugin, consider restricting access to the Jenkins interface and monitoring for any suspicious activity.

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