How severe is GHSA-vf78-3q9f-92g3?

GHSA-vf78-3q9f-92g3 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-vf78-3q9f-92g3?

GHSA-vf78-3q9f-92g3 affects the following packages: org.folio:mod-data-export-spring (Maven), org.folio:mod-data-export-spring (Maven). Ecosystems affected: Maven.

How do I fix GHSA-vf78-3q9f-92g3?

Update org.folio:mod-data-export-spring to 2.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vf78-3q9f-92g3 is resolved across your whole dependency graph.

How do I detect GHSA-vf78-3q9f-92g3 in my Maven dependencies?

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

How do I mitigate GHSA-vf78-3q9f-92g3 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-vf78-3q9f-92g3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vf78-3q9f-92g3 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-vf78-3q9f-92g3?

GHSA-vf78-3q9f-92g3 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 GHSA-vf78-3q9f-92g3?

GHSA-vf78-3q9f-92g3 is classified as Hard-coded Credentials (CWE-798). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vf78-3q9f-92g3 published, and has it been updated?

GHSA-vf78-3q9f-92g3 was published on July 25, 2023 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

CRITICAL severity

Hard-coded System User Credentials in Folio Data Export Spring moduleGHSA-vf78-3q9f-92g3

CRITICALFix: folio-org/mod-data-export-spring@93aff45

GHSA-vf78-3q9f-92g3 is a critical-severity (CVSS 10) Hard-coded Credentials vulnerability in org.folio:mod-data-export-spring. A fix is available for org.folio:mod-data-export-spring — see the affected versions and patch details below.

Also known asCVE-2024-23687

Published

Jul 25, 2023

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vf78-3q9f-92g3.

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

2 pkgs affected

☕org.folio:mod-data-export-spring☕org.folio:mod-data-export-spring

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

Impact

The module creates a system user that is used to perform internal module-to-module operations. Credentials for this user are hard-coded in the source code. This makes it trivial to authenticate as this user, resulting in unauthorized access to potentially dangerous APIs, allowing to view and modify configuration including single-sign-on configuration, to read, add and modify user data, and to read and transfer fees/fines in a patron's account.

Patches

Upgrade mod-data-export-spring to >=2.0.2, or a 1.5.x version >=1.5.4.

Workarounds

No known workarounds.

References

https://wiki.folio.org/x/hbMMBw - FOLIO Security Advisory with Upgrade Instructions https://github.com/folio-org/mod-data-export-spring/commit/93aff4566bff59e30f4121b5a2bda5b0b508a446 - Fix

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.folio:mod-data-export-spring`	≥ 2.0.0&&< 2.0.2	2.0.2`org.folio:mod-data-export-spring:2.0.2`
☕Maven	`org.folio:mod-data-export-spring`	all versions	1.5.4`org.folio:mod-data-export-spring:1.5.4`

Affected Products

1 product · 2 configurations

Application

mod-data-export-springopenlibraryfoundation

≥ 2.0.0 && < 2.0.2

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.folio:mod-data-export-spring, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.folio:mod-data-export-spring to 2.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vf78-3q9f-92g3 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact The module creates a system user that is used to perform internal module-to-module operations. Credentials for this user are hard-coded in the source code. This makes it trivial to authenticate as this user, resulting in unauthorized access to potentially dangerous APIs, allowing to view and modify configuration including single-sign-on configuration, to read, add and modify user data, and to read and transfer fees/fines in a patron's account. ### Patches Upgrade mod-data-export-spring to >=2.0.2, or a 1.5.x version >=1.5.4. ### Workarounds No known workarounds. ### References