Vulnerability Database · Maven · Package report

org.jenkins-ci.plugins:plain-credentials: vulnerability history, versions and safety

org.jenkins-ci.plugins:plain-credentials is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 19 releases, first recorded in Jun 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.jenkins-ci.plugins:plain-credentials 199.v9f8e1f741799 i

Updated on 23 Oct 2026

Good news: 199.v9f8e1f741799, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 77/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

What to do: Stay on 199.v9f8e1f741799 or newer. This can change: a vulnerability disclosed tomorrow can affect 199.v9f8e1f741799 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 199.v9f8e1f741799 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 26 Jun 2024 i
  • Highest CVSS 4.3 i
  • With no published fix 0 i
  • Depended on by 115 packages i
  • Stars 10 i
  • Last release 15 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.jenkins-ci.plugins:plain-credentials, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
199.v9f8e1f741799 27 Jun 2025 none MIT — Details →
195.vb_906e9073dee 25 Mar 2025 none MIT — Details →
183.va_de8f1dd5a_2b_ 19 Jun 2024 M1 MIT Yes Details →
182.v468b_97b_9dcb_8 14 May 2024 M1 MIT Yes Details →
179.vc5cb_98f6db_38 04 Mar 2024 M1 MIT Yes Details →
177.vb_231f25527e7 04 Mar 2024 M1 MIT Yes Details →
143.v1b_df8b_d3b_e48 03 Jan 2023 M1 MIT Yes Details →
139.ved2b_9cf7587b 28 Jul 2022 M1 MIT Yes Details →
1.8 25 Jan 2022 M1 MIT Yes Details →
1.7 29 Jan 2020 M1 MIT Yes Details →
1.6 28 Jan 2020 M1 MIT Yes Details →
1.5 11 Dec 2018 M1 MIT Yes Details →
1.4 15 Feb 2017 M1 MIT Yes Details →
1.3 26 Sep 2016 M1 MIT Yes Details →
1.2 19 May 2016 M1 MIT Yes Details →
1.1 15 Jan 2015 M1 MIT Yes Details →
1.0 16 Jun 2014 M1 MIT Yes Details →
1.0-beta-4 01 Oct 2013 M1 MIT Yes Details →
1.0-beta-3 22 Sep 2013 M1 MIT Yes Details →
1.0-beta-2 22 Sep 2013 M1 MIT Yes Details →
1.0-beta-1 22 Sep 2013 M1 MIT Yes Details →

All 21 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.jenkins-ci.plugins:plain-credentials

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 →

Questions

About org.jenkins-ci.plugins:plain-credentials

Is org.jenkins-ci.plugins:plain-credentials safe to use?

Vulert records 1 vulnerabilities for org.jenkins-ci.plugins:plain-credentials in Maven: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.jenkins-ci.plugins:plain-credentials's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:plain-credentials 77/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.jenkins-ci.plugins:plain-credentials affected?

No. 199.v9f8e1f741799, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.jenkins-ci.plugins:plain-credentials should I use?

199.v9f8e1f741799 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.jenkins-ci.plugins:plain-credentials have?

1 vulnerability is recorded for org.jenkins-ci.plugins:plain-credentials in the Maven ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.jenkins-ci.plugins:plain-credentials vulnerabilities disclosed?

0 vulnerabilities were recorded for org.jenkins-ci.plugins:plain-credentials in the last 12 months, and the oldest entry in this database dates to 26 Jun 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.jenkins-ci.plugins:plain-credentials are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.jenkins-ci.plugins:plain-credentials for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.jenkins-ci.plugins:plain-credentials version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.