Vulnerabilities in pkg:maven/io.jenkins.plugins/testsigma

PACKAGE
Advisory Identifier: GHSA-8wp4-r84g-gcmw
Advisory Summary

CVE-2025-53661 is a LOW (CVSS 3.1) jenkins testsigma test plan vulnerability vulnerability (CWE-522: Insufficiently Protected Credentials) affecting Testsigma libraries in the Maven ecosystem. The issue involves jenkins testsigma test plan vulnerability exposes api keys via job configuration form. Remediation is available in the latest vendor maintenance releases.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/io.jenkins.plugins/testsigma

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/io.jenkins.plugins/testsigma. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-8wp4-r84g-gcmw CVE-2025-53661 LOW Jenkins Testsigma Test Plan vulnerability exposes API keys via job configuration form

CVE-2025-53661 at a Glance

CVE Identifier CVE-2025-53661
GHSA Identifier GHSA-8wp4-r84g-gcmw
Severity LOW
CVSS v3.1 Base Score 3.1
CWE Classification CWE-522: Insufficiently Protected Credentials
Affected Product Testsigma
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 3.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-53661

To remediate this vulnerability, upgrade all affected Testsigma dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

io.jenkins.plugins:testsigma fixed: Latest secure release
<dependency>
    <groupId>io.jenkins.plugins</groupId>
    <artifactId>testsigma</artifactId>
    <version>Latest secure release</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=io.jenkins.plugins

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-53661, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=io.jenkins.plugins

Analyze the terminal output to locate any version of Testsigma in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree -Dincludes=io.jenkins.plugins command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In Testsigma, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Jenkins Testsigma Test Plan run Plugin stores Testsigma API keys in job `config.xml` files on the Jenkins controller as part of its configuration. While these API keys are stored encrypted on disk, in Testsigma Test Plan run Plugin 1.6 and earlier, the job configuration form does not mask these API keys, increasing the potential for attackers to observe and capture them. As of publication of this advisory, there is no fix.

CVE-2025-53661 Affected Testsigma Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
io.jenkins.plugins:testsigma
Maven
≤ 1.6

References

Frequently Asked Questions

What is CVE-2025-53661?
CVE-2025-53661 is a security vulnerability in Testsigma involving Jenkins Testsigma Test Plan vulnerability exposes API keys via job configuration form under CWE-522: Insufficiently Protected Credentials.
Which Testsigma versions are affected?
Affected versions include releases prior to current release patches across affected packages: io.jenkins.plugins:testsigma.
What version fixes CVE-2025-53661?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is testsigma affected?
Yes, io.jenkins.plugins:testsigma is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2025-53661?
CVE-2025-53661 has a CVSS v3.1 base score of 3.1 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2025-53661?
CVE-2025-53661 is classified under CWE-522: Insufficiently Protected Credentials (The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.).
How can I check Maven dependencies for CVE-2025-53661?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=io.jenkins.plugins'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8wp4-r84g-gcmw",
  "modified" : "2025-11-05T20:00:45Z",
  "published" : "2025-07-09T18:30:46Z",
  "aliases" : [ "CVE-2025-53661" ],
  "summary" : "Jenkins Testsigma Test Plan vulnerability exposes API keys via job configuration form",
  "details" : "Jenkins Testsigma Test Plan run Plugin stores Testsigma API keys in job `config.xml` files on the Jenkins controller as part of its configuration.\n\nWhile these API keys are stored encrypted on disk, in Testsigma Test Plan run Plugin 1.6 and earlier, the job configuration form does not mask these API keys, increasing the potential for attackers to observe and capture them.\n\nAs of publication of this advisory, there is no fix.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.jenkins.plugins:testsigma"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-53661"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jenkinsci/testsigma-plugin"
  }, {
    "type" : "WEB",
    "url" : "https://www.jenkins.io/security/advisory/2025-07-09/#SECURITY-3515"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2025/07/09/4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-522" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-07-09T21:14:44Z",
    "nvd_published_at" : "2025-07-09T16:15:25Z"
  }
}