How severe is CVE-2020-2315?

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

Which packages are affected by CVE-2020-2315?

CVE-2020-2315 affects the following packages: org.jenkins-ci.plugins:visualworks-store (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-2315?

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

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

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

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

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

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

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

CVE-2020-2315 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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.

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

CVE-2020-2315 was published on November 4, 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-2315 — visualworks-store

MEDIUMFix: jenkinsci/visualworks-store-plugin@267bb70

CVE-2020-2315 is a medium-severity (CVSS 6.5) vulnerability in org.jenkins-ci.plugins:visualworks-store. A fix is available for org.jenkins-ci.plugins:visualworks-store — see the affected versions and patch details below.

XXE vulnerability in Jenkins Visualworks Store Plugin

Also known asGHSA-jvjm-j945-8qwc

Published

Nov 4, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% 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:visualworks-store

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 Visualworks Store Plugin 1.1.3 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

This allows attackers with the ability to control the output of a script that run Visualworks with StoreCI, or able to control an agent process, to have Jenkins parse a crafted file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.

Jenkins Visualworks Store Plugin 1.1.4 disables external entity resolution for its XML parser.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:visualworks-store`	all versions	1.1.4`org.jenkins-ci.plugins:visualworks-store:1.1.4`

Affected Products

1 product · 1 configurations

Application

visualworks storejenkins

≤ 1.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:visualworks-store, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:visualworks-store to 1.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2315 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

Jenkins Visualworks Store Plugin 1.1.3 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. This allows attackers with the ability to control the output of a script that run Visualworks with StoreCI, or able to control an agent process, to have Jenkins parse a crafted file that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery. Jenkins Visualworks Store Plugin 1.1.4 disables external entity resolution for its XML parser.

O3 Security · Impact-Aware SCA

Is CVE-2020-2315 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works