VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

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

org.jenkins-ci.plugins:badge is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 10 releases, from Jan 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 M2
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:badge vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:badge 3.615.vb_ed967ca_b_e93 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 3.615.vb_ed967ca_b_e93 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 14 May 2022 i
  • Highest CVSS 5.4 i
  • With no published fix 0 i
  • Stars 40 i
  • Last release this month 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:badge, 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
3.615.vb_ed967ca_b_e93 24 Sep 2026 none non-standard — Details →
3.605.v7a_3387b_97a_b_6 21 Jul 2026 none non-standard — Details →
3.591.v9074c6c6f0b_9 14 Apr 2026 none non-standard — Details →
3.590.v1c3de0b_d2fb_2 13 Apr 2026 none non-standard — Details →
3.586.v96c477844983 07 Apr 2026 none non-standard — Details →
3.583.vdc8d4a_a_1d586 25 Mar 2026 none non-standard — Details →
2.562.vc3c0b_6925377 15 Dec 2025 none non-standard — Details →
2.560.v5135054c2e76 11 Dec 2025 none non-standard — Details →
2.12 29 Oct 2025 none non-standard — Details →
2.11 01 Oct 2025 none non-standard — Details →
2.10 11 Sep 2025 none non-standard — Details →
2.9.1 31 Jul 2025 none non-standard — Details →
2.9 31 Jul 2025 none non-standard — Details →
2.8 10 Apr 2025 none non-standard — Details →
2.7 25 Feb 2025 none non-standard — Details →
2.6 10 Feb 2025 none non-standard — Details →
2.5 11 Nov 2024 none non-standard — Details →
2.4 04 Nov 2024 none non-standard — Details →
2.3 23 Oct 2024 none non-standard — Details →
2.2 07 Oct 2024 none non-standard — Details →
2.1 17 Sep 2024 none non-standard — Details →
2.0 16 Sep 2024 none non-standard — Details →
1.13 01 Jun 2024 none non-standard — Details →
1.12 21 May 2024 none non-standard — Details →
1.11 17 May 2024 none non-standard — Details →
1.10 11 May 2024 none non-standard — Details →
1.4 13 Feb 2024 M2 non-standard Yes Details →
1.9.1 13 Feb 2024 none non-standard — Details →
1.3 13 Feb 2024 M2 non-standard Yes Details →
1.6 13 Feb 2024 M1 non-standard Yes Details →
1.0 13 Feb 2024 M2 non-standard Yes Details →
1.7 13 Feb 2024 M1 non-standard Yes Details →
1.5 13 Feb 2024 M1 non-standard Yes Details →
1.2 13 Feb 2024 M2 non-standard Yes Details →
1.1 13 Feb 2024 M2 non-standard Yes Details →
1.8 13 Feb 2024 M1 non-standard Yes Details →
1.9 13 Feb 2024 M1 non-standard Yes Details →

All 37 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:badge

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-23108: Stored XSS vulnerability in Jenkins Badge Plugin 5.4 medium 1.9.1 13 Jan 2022
CVE-2018-1000604: Jenkins Badge Plugin cross-site scripting vulnerability 5.4 medium 1.5 14 May 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:badge

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

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

Vulert scores org.jenkins-ci.plugins:badge 76/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:badge affected?

No. 3.615.vb_ed967ca_b_e93, 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:badge should I use?

3.615.vb_ed967ca_b_e93 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:badge have?

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

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

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