How severe is GHSA-jvjm-j945-8qwc?

GHSA-jvjm-j945-8qwc 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 GHSA-jvjm-j945-8qwc?

GHSA-jvjm-j945-8qwc affects the following packages: org.jenkins-ci.plugins:visualworks-store (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jvjm-j945-8qwc?

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 GHSA-jvjm-j945-8qwc is resolved across your whole dependency graph.

How do I detect GHSA-jvjm-j945-8qwc 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 GHSA-jvjm-j945-8qwc 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.

How does O3 Security protect against GHSA-jvjm-j945-8qwc?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jvjm-j945-8qwc can be triaged on real exposure rather than presence alone.

Is GHSA-jvjm-j945-8qwc actively exploited in the wild?

No public exploit code has been indexed for GHSA-jvjm-j945-8qwc 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 GHSA-jvjm-j945-8qwc?

GHSA-jvjm-j945-8qwc has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 64th 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 GHSA-jvjm-j945-8qwc published, and has it been updated?

GHSA-jvjm-j945-8qwc 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

GHSA-jvjm-j945-8qwc — visualworks-store

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

GHSA-jvjm-j945-8qwc 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 asCVE-2020-2315

Published

May 24, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 20, 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 CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-jvjm-j945-8qwc plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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`

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 GHSA-jvjm-j945-8qwc 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jvjm-j945-8qwc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-jvjm-j945-8qwc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-jvjm-j945-8qwc in your dependencies?

O3 Security finds GHSA-jvjm-j945-8qwc across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works