How severe is CVE-2020-2260?

CVE-2020-2260 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-2260?

CVE-2020-2260 affects the following packages: io.jenkins.plugins:perfecto (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-2260?

Update io.jenkins.plugins:perfecto to 1.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2260 is resolved across your whole dependency graph.

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

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

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2020-2260 actively exploited in the wild?

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

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

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

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

CVE-2020-2260 was published on September 16, 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-2260 — perfecto

MEDIUM

CVE-2020-2260 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in io.jenkins.plugins:perfecto. A fix is available for io.jenkins.plugins:perfecto — see the affected versions and patch details below.

Missing permission check in Perfecto Plugin

Also known asGHSA-3h2q-m63q-9cf6

Published

Sep 16, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% 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

☕io.jenkins.plugins:perfecto

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

Perfecto Plugin 1.17 and earlier does not perform a permission check in a method implementing a connection test.

This allows attackers with Overall/Read permission to connect to an attacker-specified HTTP URL using attacker-specified username and password.

Perfecto Plugin 1.18 requires Overall/Administer permission to perform a connection test.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jenkins.plugins:perfecto`	all versions	1.18`io.jenkins.plugins:perfecto:1.18`

Affected Products

1 product · 1 configurations

Application

perfectojenkins

≤ 1.17

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:perfecto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:perfecto to 1.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2260 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Perfecto Plugin 1.17 and earlier does not perform a permission check in a method implementing a connection test. This allows attackers with Overall/Read permission to connect to an attacker-specified HTTP URL using attacker-specified username and password. Perfecto Plugin 1.18 requires Overall/Administer permission to perform a connection test.

O3 Security · Impact-Aware SCA

Is CVE-2020-2260 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

None

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-862CWE-862

Weaponization

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

Timeline

Disclosed

Sep 16, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2020-2260

GHSA-3h2q-m63q-9cf6

References

Advisoryopenwall.com Advisoryjenkins.io · 2020 09 16 Advisorynvd.nist.gov · CVE 2020 2260 Packagegithub.com · perfecto plugin

Related vulnerabilities

Also affects perfecto

This CVE is medium severity; 1 of 1 other CVE affecting perfecto is rated as high or higher (top: high).

CVE-2020-2261

Same weakness: CWE-862

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

GHSA-47w9-6r3f-938gCVE-2026-16454CVE-2026-12411CVE-2026-93363CVE-2026-116677CVE-2026-116794CVE-2026-118759Browse all CWE-862

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-2260 — perfecto

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