How severe is CVE-2019-10359?

CVE-2019-10359 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-10359?

CVE-2019-10359 affects the following packages: org.jenkins-ci.plugins.m2release:m2release (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-10359?

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

How do I detect CVE-2019-10359 in my Maven dependencies?

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

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

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

CVE-2019-10359 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th 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-2019-10359?

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

CVE-2019-10359 was published on May 24, 2022 and was last updated on February 16, 2024. 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-2019-10359 — m2release

MEDIUMFix: jenkinsci/m2release-plugin@2f1117d

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

Jenkins Maven Release Plugin contains Cross-Site Request Forgery vulnerability

Published

May 24, 2022

Updated

Feb 16, 2024

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.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% 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.m2release:m2release

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

A cross-site request forgery vulnerability in Jenkins Maven Release Plugin 0.14.0 and earlier in the M2ReleaseAction#doSubmit method allowed attackers to perform releases with attacker-specified options.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins.m2release:m2release`	all versions	0.15.0`org.jenkins-ci.plugins.m2release:m2release:0.15.0`

Affected Products

1 product · 1 configurations

Application

m2releasejenkins

≤ 0.14.0

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

A cross-site request forgery vulnerability in Jenkins Maven Release Plugin prior to 0.15.0 in the M2ReleaseAction#doSubmit method allowed attackers to perform releases with attacker-specified options.

O3 Security · Impact-Aware SCA

Is CVE-2019-10359 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Raw vector

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

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

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

Timeline

Disclosed

May 24, 2022

Last updated

Feb 16, 2024

Identifiers

CVE-2019-10359

References

Advisorynvd.nist.gov · CVE 2019 10359 Webgithub.com · 2f1117d011e1ef200f28bbb0c24bf918b89704b6 Webjenkins.io · 2019 07 31 Webopenwall.com Packagegithub.com · m2release plugin

Related vulnerabilities

Also affects m2release

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

CVE-2019-10360CVE-2019-16549CVE-2019-16550CVE-2019-10361

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-96629CVE-2026-118266CVE-2026-113796CVE-2026-84312Browse all CWE-352

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024