How severe is CVE-2020-2239?

CVE-2020-2239 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-2239?

CVE-2020-2239 affects the following packages: org.jenkins-ci.plugins:Parameterized-Remote-Trigger (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-2239?

Update org.jenkins-ci.plugins:Parameterized-Remote-Trigger to 3.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2239 is resolved across your whole dependency graph.

How do I detect CVE-2020-2239 in my Maven dependencies?

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

How do I mitigate CVE-2020-2239 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-2020-2239 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-2239 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-2020-2239?

CVE-2020-2239 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th 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-2020-2239?

CVE-2020-2239 is classified as CWE-311 (CWE-311). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-2239 published, and has it been updated?

CVE-2020-2239 was published on September 1, 2020 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

MEDIUM severity

CVE-2020-2239 — Parameterized-Remote-Trig…

MEDIUMFix: jenkinsci/parameterized-remote-trigger-plugin@2902ef5

CVE-2020-2239 is a medium-severity (CVSS 4.3) CWE-311 vulnerability in org.jenkins-ci.plugins:Parameterized-Remote-Trigger. A fix is available for org.jenkins-ci.plugins:Parameterized-Remote-Trigger — see the affected versions and patch details below.

Secret stored in plain text by Jenkins Parameterized Remote Trigger Plugin

Also known asGHSA-wphq-j78p-fhgp

Published

Sep 1, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% 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:Parameterized-Remote-Trigger

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

Parameterized Remote Trigger Plugin 3.1.3 and earlier stores a secret unencrypted in its global configuration file org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.xml on the Jenkins controller as part of its configuration. This secret can be viewed by attackers with access to the Jenkins controller file system.

Parameterized Remote Trigger Plugin 3.1.4 stores the secret encrypted once its configuration is saved again.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:Parameterized-Remote-Trigger`	all versions	3.1.4`org.jenkins-ci.plugins:Parameterized-Remote-Trigger:3.1.4`

Affected Products

1 product · 1 configurations

Application

parameterized remote triggerjenkins

≤ 3.1.3

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:Parameterized-Remote-Trigger, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:Parameterized-Remote-Trigger to 3.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2239 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

Parameterized Remote Trigger Plugin 3.1.3 and earlier stores a secret unencrypted in its global configuration file `org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.xml` on the Jenkins controller as part of its configuration. This secret can be viewed by attackers with access to the Jenkins controller file system. Parameterized Remote Trigger Plugin 3.1.4 stores the secret encrypted once its configuration is saved again.

O3 Security · Impact-Aware SCA

Is CVE-2020-2239 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-311CWE-311

Weaponization

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

Timeline

Disclosed

Sep 1, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2020-2239

GHSA-wphq-j78p-fhgp

References

Advisoryopenwall.com Advisoryjenkins.io · 2020 09 01 Advisorynvd.nist.gov · CVE 2020 2239 Webgithub.com · 2902ef5ea6eb077f43fd25c880e4920faea4e828 Packagegithub.com · parameterized remote trigger plugin

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs with CWE-311 are rated as high or higher (top: critical).

CVE-2026-111063GHSA-464c-974j-9xm6CVE-2026-54784CVE-2026-55568CVE-2026-53442CVE-2026-34486CVE-2026-34992CVE-2026-27944Browse all CWE-311

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-2239 — Parameterized-Remote-Trig…

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-2020-2239 in your dependencies?