Hard-coded System User Credentials in Folio Data Export Spring module

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

EPSS

• CVE-2024-23687: 0.65% estimated exploitation activity in the next 30 days; percentile 51.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

25 Jul 2023, 13:53 UTC

Last modified by the source

22 Jan 2026, 20:30 UTC

Source last checked

26 Oct 2026, 16:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vf78-3q9f-92g3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-23687

Advisory: Hard-coded System User Credentials in Folio Data Export Spring module
IDs: CVE-2024-23687, GHSA-vf78-3q9f-92g3
Record: https://patchnext.com/advisories/cve-2024-23687 (revision 1, source checked 26 Oct 2026, 16:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.folio:mod-data-export-spring 2.0.2, 1.5.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.folio:mod-data-export-spring: affected >= 2.0.0, < 2.0.2; < 1.5.4; fixed in 1.5.4, 2.0.2

## Suggested inspection (read-only)
- Maven org.folio:mod-data-export-spring: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.folio:mod-data-export-spring.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vf78-3q9f-92g3 (GitHub-reviewed advisory GHSA-vf78-3q9f-92g3 lists affected ranges: Maven org.folio:mod-data-export-spring >=2.0.0 =0 <1.5.4)

Commands are suggestions: review each one before running it.