CVE-2025-53669VulnerabilityPublished 9 Jul 2025Updated 5 Nov 2025

Org.jenkins ci.plugins:vaddy plugin: Jenkins VAddy Plugin vulnerability exposes plaintext keys on its job

Affects org.jenkins-ci.plugins:vaddy-pluginSource GCVE Database

Compare

Authoritative record:CVE-2025-53669· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 4 Nov 2026, 18:14 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	4.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.jenkins-ci.plugins:vaddy-plugin	Affected <=1.2.8	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should restrict access to Jenkins job configurations to trusted personnel only to reduce the risk of key exposure. Monitor vendor advisories for any forthcoming patches or updates addressing this issue.

Description

Jenkins VAddy Plugin versions 1.2.8 and earlier do not mask Vaddy API authentication keys in the job configuration form. This vulnerability allows these keys to be visible in plaintext, increasing the risk that an attacker with access to the job configuration could observe and capture them. The vulnerability has a medium severity rating with a CVSS score of 4.3.

Impact

Exposure of Vaddy API authentication keys in plaintext increases the risk of credential compromise if an attacker gains access to the Jenkins job configuration. This could lead to unauthorized API calls using the stolen keys. The impact is limited to confidentiality (partial loss), with no direct integrity or availability effects reported.

Summary

The Jenkins VAddy Plugin up to version 1.2.8 exposes Vaddy API authentication keys in plaintext on the job configuration form. This lack of masking means that anyone with access to the job configuration interface can see the keys directly, potentially leading to unauthorized use of the API credentials. The vulnerability is identified as CWE-256 (Plaintext Storage of a Password). There is no indication of active exploitation in the wild or available patches at this time.

CWE-256Plaintext Storage of a Password (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores a password in plaintext within resources such as memory or files.
Architecture and Design
Avoid storing passwords in easily accessible locations.
Architecture and Design
Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.
A programmer might attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password because the encoding can be detected and decoded easily.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.7.5 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 18:14 UTC

WeaknessesCWE-256

Technical details

References

Community reviews

Related threats