How severe is CVE-2021-21629?

CVE-2021-21629 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-21629?

CVE-2021-21629 affects the following packages: org.jenkins-ci.plugins:build-with-parameters (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-21629?

Update org.jenkins-ci.plugins:build-with-parameters to 1.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21629 is resolved across your whole dependency graph.

How do I detect CVE-2021-21629 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:build-with-parameters, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-21629 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2021-21629 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-21629 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-21629?

CVE-2021-21629 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-21629?

CVE-2021-21629 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-21629 published, and has it been updated?

CVE-2021-21629 was published on March 30, 2021 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2021-21629 — build-with-parameters

HIGHFix: jenkinsci/build-with-parameters-plugin@82711e8

CVE-2021-21629 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in org.jenkins-ci.plugins:build-with-parameters. A fix is available for org.jenkins-ci.plugins:build-with-parameters — see the affected versions and patch details below.

CSRF vulnerability in Jenkins Build With Parameters Plugin

Also known asGHSA-w24g-24qg-v4w2

Published

Mar 30, 2021

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:build-with-parameters

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins Build With Parameters Plugin 1.5 and earlier does not require POST requests for its form submission endpoint, resulting in a cross-site request forgery (CSRF) vulnerability.

This vulnerability allows attackers to build a project with attacker-specified parameters. Build With Parameters Plugin 1.5.1 requires POST requests for the affected HTTP endpoint.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:build-with-parameters`	all versions	1.5.1`org.jenkins-ci.plugins:build-with-parameters:1.5.1`

Affected Products

1 product · 1 configurations

Application

build with parametersjenkins

≤ 1.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:build-with-parameters, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:build-with-parameters to 1.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21629 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Jenkins Build With Parameters Plugin 1.5 and earlier does not require POST requests for its form submission endpoint, resulting in a cross-site request forgery (CSRF) vulnerability. This vulnerability allows attackers to build a project with attacker-specified parameters. Build With Parameters Plugin 1.5.1 requires POST requests for the affected HTTP endpoint.

O3 Security · Impact-Aware SCA

Is CVE-2021-21629 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Mar 30, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2021-21629

GHSA-w24g-24qg-v4w2

References

Advisoryopenwall.com Advisoryjenkins.io · 2021 03 30 Advisorynvd.nist.gov · CVE 2021 21629 Webgithub.com · 82711e83bf822c5688017304939d5d1c3482ec3e Packagegithub.com · build with parameters plugin

Related vulnerabilities

Also affects build-with-parameters

This CVE is high severity — higher than any of the other 1 CVE affecting build-with-parameters (highest there: moderate).

CVE-2021-21628

Same weakness: CWE-352

This CVE is high severity; 2 of 7 other CVEs with CWE-352 are rated as high or higher (top: high).

CVE-2026-96629CVE-2026-118266CVE-2026-113796CVE-2026-84312CVE-2026-62322CVE-2026-107809CVE-2026-107848Browse all CWE-352

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2021-21629 — build-with-parameters

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-21629 in your dependencies?