Hard-coded credentials in FOLIO mod-data-export-spring versions before 1.5.4 and from 2.0.0 to 2.0.2 allows unauthenticated users to access critical APIs, modify user data, modify configurations including single-sign-on, and manipulate fees/fines.
Security readout for executives and security teams
Plain-English summary
CVE-2024-23687 is a critical hard-coded credential issue in FOLIO mod-data-export-spring. An unauthenticated attacker could use exposed credentials to reach critical APIs and alter user data, SSO-related configuration, and fees or fines. This is high business urgency for affected FOLIO deployments.
Executive priority
Treat as urgent for any organization running affected FOLIO versions. Prioritize confirmation and upgrade because the issue can enable unauthenticated changes to identity-related configuration and patron financial records.
Technical view
Affected org.folio:mod-data-export-spring versions before 1.5.4 and 2.0.0 through 2.0.2 contain hard-coded credentials. The vulnerability is network exploitable with low complexity, no privileges, and no user interaction. CVSS 3.1 is 9.1 with high confidentiality and integrity impact.
Likely exposure
Exposure is limited to FOLIO deployments using org.folio:mod-data-export-spring in the listed affected version ranges. Internet-facing or broadly reachable FOLIO APIs would raise operational risk, but the supplied sources do not define deployment prevalence.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk remains serious because the issue is unauthenticated, network reachable, and affects critical administrative and data-changing APIs.
Researcher notes
Evidence supports CWE-798 hard-coded credentials with critical API access. Do not assume exploitation in the wild from the supplied data. Focus validation on version inventory, patch presence, access review, and integrity checks for the impacted FOLIO data domains.
Mitigation direction
Upgrade off affected versions before 1.5.4 and 2.0.0 through 2.0.2.
Apply vendor guidance from the GitHub advisory and linked patch.
Restrict network access to FOLIO administrative APIs where operationally possible.
Rotate any credentials that may have been exposed or reused.
Review SSO, user, fee, and fine configuration changes after remediation.
Validation and detection
Inventory all FOLIO deployments for org.folio:mod-data-export-spring usage.
Compare installed versions against the affected ranges in the advisory.
Confirm the patched package or vendor-fixed release is deployed.
Review logs for unauthenticated access to sensitive mod-data-export APIs.
Validate user data, SSO settings, fees, and fines for unauthorized changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-798 · source CWE mapping
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.