How severe is CVE-2022-20613?

CVE-2022-20613 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-2022-20613?

CVE-2022-20613 affects the following packages: org.jenkins-ci.plugins:mailer (Maven), org.jenkins-ci.plugins:mailer (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-20613?

Update org.jenkins-ci.plugins:mailer to 408.vd726a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-20613 is resolved across your whole dependency graph.

How do I detect CVE-2022-20613 in my Maven dependencies?

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

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

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

CVE-2022-20613 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 60th 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-2022-20613?

CVE-2022-20613 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-2022-20613 published, and has it been updated?

CVE-2022-20613 was published on January 12, 2022 and was last updated on July 8, 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-2022-20613 — mailer

MEDIUMFix: jenkinsci/mailer-plugin@5e6051f

CVE-2022-20613 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in org.jenkins-ci.plugins:mailer. A fix is available for org.jenkins-ci.plugins:mailer — see the affected versions and patch details below.

Cross-Site Request Forgery in Jenkins Mailer Plugin

Also known asGHSA-85rq-hp8x-ghjq

Published

Jan 12, 2022

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2022-20613 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.jenkins-ci.plugins:mailer☕org.jenkins-ci.plugins:mailer

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 Mailer Plugin prior to 408.vd726a_1130320 and 1.34.2 does not perform a permission check in a method implementing form validation.

This allows attackers with Overall/Read access to use the DNS used by the Jenkins instance to resolve an attacker-specified hostname.

Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

Mailer Plugin 408.vd726a_1130320 and 1.34.2 require POST requests and Overall/Administer permission for the affected form validation method.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:mailer`	≥ 391.ve4a38c1bcf4b&&< 408.vd726a	408.vd726a`org.jenkins-ci.plugins:mailer:408.vd726a`
☕Maven	`org.jenkins-ci.plugins:mailer`	all versions	1.34.2`org.jenkins-ci.plugins:mailer:1.34.2`

Affected Products

2 products · 3 configurations

Application

mailerjenkins

< 1.34.2

1 version

391.ve4a_38c1b_cf4b_

Application

communications cloud native core automated test suiteoracle

1 version

1.9.0

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:mailer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:mailer to 408.vd726a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-20613 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 Mailer Plugin prior to 408.vd726a_1130320 and 1.34.2 does not perform a permission check in a method implementing form validation. This allows attackers with Overall/Read access to use the DNS used by the Jenkins instance to resolve an attacker-specified hostname. Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability. Mailer Plugin 408.vd726a_1130320 and 1.34.2 require POST requests and Overall/Administer permission for the affected form validation method.

O3 Security · Impact-Aware SCA

Is CVE-2022-20613 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

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Jan 12, 2022

Last updated

Jul 8, 2026

Identifiers

CVE-2022-20613

GHSA-85rq-hp8x-ghjq

References

Advisoryopenwall.com Advisoryjenkins.io Advisorynvd.nist.gov Fixoracle.com Webgithub.com Packagegithub.com

Related vulnerabilities

Also affects mailer

This CVE is medium severity; 3 of 4 other CVEs affecting mailer are rated as high or higher (top: high).

CVE-2020-2252CVE-2018-8718CVE-2017-2651CVE-2022-20614

Same weakness: CWE-352

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

CVE-2026-61593CVE-2026-59148CVE-2026-73222CVE-2026-73292Browse all CWE-352

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026

CVE-2022-20613 — mailer

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