VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

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

org.jenkins-ci.plugins:token-macro is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 26 releases, first recorded in 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 H1 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.

See all org.jenkins-ci.plugins:token-macro vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:token-macro 477.vd4f0dc3cb_cf1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 477.vd4f0dc3cb_cf1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 17 packages i
  • Stars 22 i
  • Last release 14 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:token-macro, 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
477.vd4f0dc3cb_cf1 30 Jul 2025 none non-standard — Details →
444.v52de7e9c573d 04 Feb 2025 none non-standard — Details →
442.v4f452dc3c7c0 02 Feb 2025 none non-standard — Details →
1.2 13 Feb 2024 H1 M1 — Yes Details →
1.7 13 Feb 2024 H1 M1 — Yes Details →
1.9 13 Feb 2024 H1 M1 — Yes Details →
277.v7c8f82a_d66b_3 13 Feb 2024 none non-standard — Details →
2.10 13 Feb 2024 none non-standard — Details →
266.v44a80cf277fd 13 Feb 2024 none non-standard — Details →
1.12 13 Feb 2024 H1 M1 non-standard Yes Details →
2.2 13 Feb 2024 H1 M1 non-standard Yes Details →
2.0 13 Feb 2024 H1 M1 non-standard Yes Details →
2.0-beta 13 Feb 2024 H1 M1 non-standard Yes Details →
1.4 13 Feb 2024 H1 M1 — Yes Details →
1.5 13 Feb 2024 H1 M1 — Yes Details →
1.12.1 13 Feb 2024 H1 M1 non-standard Yes Details →
267.vcdaea6462991 13 Feb 2024 none non-standard — Details →
2.1 13 Feb 2024 H1 M1 non-standard Yes Details →
2.3 13 Feb 2024 H1 M1 non-standard Yes Details →
400.v35420b_922dcb_ 13 Feb 2024 none non-standard — Details →
2.8 13 Feb 2024 none non-standard — Details →
1.3 13 Feb 2024 H1 M1 — Yes Details →
1.10 13 Feb 2024 H1 M1 non-standard Yes Details →
1.6 13 Feb 2024 H1 M1 — Yes Details →
2.15 13 Feb 2024 none — — Details →
2.6 13 Feb 2024 H1 non-standard Yes Details →
383.v36161104b_002 13 Feb 2024 none non-standard — Details →
1.5.1 13 Feb 2024 H1 M1 — Yes Details →
1.1 13 Feb 2024 H1 M1 — Yes Details →
2.14 13 Feb 2024 none — — Details →
2.5 13 Feb 2024 H1 M1 non-standard Yes Details →
2.11 13 Feb 2024 none non-standard — Details →
1.13-alpha 13 Feb 2024 H1 M1 non-standard Yes Details →
2.7 13 Feb 2024 H1 non-standard Yes Details →
1.8 13 Feb 2024 H1 M1 — Yes Details →
384.vf35b_f26814ec 13 Feb 2024 none non-standard — Details →
1.11 13 Feb 2024 H1 M1 non-standard Yes Details →
270.v8c2ce50dc4fc 13 Feb 2024 none non-standard — Details →
321.vd7cc1f2a_52c8 13 Feb 2024 none non-standard — Details →
2.9 13 Feb 2024 none non-standard — Details →
2.4 13 Feb 2024 H1 M1 non-standard Yes Details →
1.8.1 13 Feb 2024 H1 M1 — Yes Details →
359.vb_cde11682e0c 13 Feb 2024 none non-standard — Details →
1.0 13 Feb 2024 H1 M1 — Yes Details →
293.v283932a_0a_b_49 13 Feb 2024 none non-standard — Details →
2.12 13 Feb 2024 none non-standard — Details →
280.v97a_82642793c 13 Feb 2024 none non-standard — Details →
285.vff7645a_56ff0 13 Feb 2024 none non-standard — Details →
308.v4f2b_ed62b_b_16 13 Feb 2024 none non-standard — Details →
2.13 13 Feb 2024 none non-standard — Details →

All 50 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:token-macro

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-10337: Jenkins Token Macro Plugin - Improper Restriction of XML External Entity Reference 7.5 high 2.8 24 May 2022
CVE-2019-1003011: Jenkins Token Macro Plugin's recursive token expansion results in information disclosure and DoS 6.5 medium 2.6 13 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:token-macro

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

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

Vulert scores org.jenkins-ci.plugins:token-macro 72/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:token-macro affected?

No. 477.vd4f0dc3cb_cf1, 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:token-macro should I use?

477.vd4f0dc3cb_cf1 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:token-macro have?

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

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

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