VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.jenkins-ci.plugins:parameterized-trigger: vulnerability history, versions and safety

org.jenkins-ci.plugins:parameterized-trigger is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 43 releases, from Mar 2022 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 L1
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.

See all org.jenkins-ci.plugins:parameterized-trigger vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:parameterized-trigger 893.va_383a_9b_a_4c11 i

Updated on 23 Oct 2026

Good news: 893.va_383a_9b_a_4c11, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 82/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 893.va_383a_9b_a_4c11 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Stars 77 i
  • Last release 5 months ago i
  • Licence non-standard 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:parameterized-trigger, 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
893.va_383a_9b_a_4c11 06 May 2026 none non-standard — Details →
890.vc240a_a_e1217f 25 Feb 2026 none non-standard — Details →
889.v851b_12208b_a_7 23 Feb 2026 none non-standard — Details →
873.v8b_e37dd8418f 08 Aug 2025 none non-standard — Details →
859.vb_e3907a_07a_16 14 Apr 2025 none non-standard — Details →
840.v3c7d4a_a_5e6c7 22 Jan 2025 none non-standard — Details →
806.vf6fff3e28c3e 07 May 2024 none non-standard — Details →
2.35 13 Feb 2024 M1 L1 non-standard Yes Details →
2.23 13 Feb 2024 M1 L1 non-standard Yes Details →
2.7 13 Feb 2024 M1 L1 — Yes Details →
787.v665fcf2a_830b_ 13 Feb 2024 none non-standard — Details →
2.46 13 Feb 2024 none non-standard — Details →
2.41 13 Feb 2024 L1 non-standard Yes Details →
2.34 13 Feb 2024 M1 L1 non-standard Yes Details →
2.24 13 Feb 2024 M1 L1 non-standard Yes Details →
2.18 13 Feb 2024 M1 L1 — Yes Details →
2.40 13 Feb 2024 L1 non-standard Yes Details →
2.22 13 Feb 2024 M1 L1 — Yes Details →
2.17 13 Feb 2024 M1 L1 — Yes Details →
2.29 13 Feb 2024 M1 L1 non-standard Yes Details →
2.26 13 Feb 2024 M1 L1 non-standard Yes Details →
2.13 13 Feb 2024 M1 L1 — Yes Details →
2.5 13 Feb 2024 M1 L1 — Yes Details →
2.14 13 Feb 2024 M1 L1 — Yes Details →
2.32 13 Feb 2024 M1 L1 non-standard Yes Details →
2.43.1 13 Feb 2024 none non-standard — Details →
2.43 13 Feb 2024 L1 non-standard Yes Details →
2.9 13 Feb 2024 M1 L1 — Yes Details →
2.12 13 Feb 2024 M1 L1 — Yes Details →
2.35.2 13 Feb 2024 L1 non-standard Yes Details →
2.41.1 13 Feb 2024 L1 non-standard Yes Details →
2.10 13 Feb 2024 M1 L1 — Yes Details →
2.45 13 Feb 2024 none non-standard — Details →
2.21 13 Feb 2024 M1 L1 — Yes Details →
2.36 13 Feb 2024 L1 non-standard Yes Details →
2.38 13 Feb 2024 L1 non-standard Yes Details →
2.31 13 Feb 2024 M1 L1 non-standard Yes Details →
2.39 13 Feb 2024 L1 non-standard Yes Details →
2.40.1 13 Feb 2024 L1 non-standard Yes Details →
2.15 13 Feb 2024 M1 L1 — Yes Details →
2.19 13 Feb 2024 M1 L1 — Yes Details →
2.35.1 13 Feb 2024 L1 non-standard Yes Details →
2.44 13 Feb 2024 none non-standard — Details →
2.28 13 Feb 2024 M1 L1 non-standard Yes Details →
2.11 13 Feb 2024 M1 L1 — Yes Details →
2.27 13 Feb 2024 M1 L1 non-standard Yes Details →
2.37 13 Feb 2024 L1 non-standard Yes Details →
2.30 13 Feb 2024 M1 L1 non-standard Yes Details →
2.20 13 Feb 2024 M1 L1 — Yes Details →
2.25 13 Feb 2024 M1 L1 non-standard Yes Details →
2.42 13 Feb 2024 L1 non-standard Yes Details →
2.8 13 Feb 2024 M1 L1 — Yes Details →
2.16 13 Feb 2024 M1 L1 — Yes Details →
2.6 13 Feb 2024 M1 L1 — Yes Details →
2.33 13 Feb 2024 M1 L1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for org.jenkins-ci.plugins:parameterized-trigger

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-1000084: Parameterized Trigger Plugin fails to check Item/Build permission in org.jenkins-ci.plugins:parameterized-trigger 6.5 medium 2.35.1 13 May 2022
CVE-2022-27195: Sensitive parameter values captured in build metadata files by Jenkins Parameterized Trigger Plugin 3.3 low 2.43.1 16 Mar 2022

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:parameterized-trigger

Is org.jenkins-ci.plugins:parameterized-trigger safe to use?

Vulert records 2 vulnerabilities for org.jenkins-ci.plugins:parameterized-trigger in Maven: 0 critical, 0 high, 1 medium and 1 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:parameterized-trigger's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:parameterized-trigger 82/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:parameterized-trigger affected?

No. 893.va_383a_9b_a_4c11, 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:parameterized-trigger should I use?

893.va_383a_9b_a_4c11 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:parameterized-trigger have?

2 vulnerabilities are recorded for org.jenkins-ci.plugins:parameterized-trigger in the Maven ecosystem: 0 critical, 0 high, 1 medium and 1 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:parameterized-trigger vulnerabilities disclosed?

0 vulnerabilities were recorded for org.jenkins-ci.plugins:parameterized-trigger in the last 12 months, and the oldest entry in this database dates to 16 Mar 2022. 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:parameterized-trigger 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:parameterized-trigger for upcoming vulnerabilities?

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