CVE-2022-4963: A vulnerability was found in Folio Spring Module Core up to 1.1.5

Q: How do I fix CVE-2022-4963?

spring module core: upgrade to 2.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-4963 being exploited?

CVE-2022-4963 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-4963 affect?

CVE-2022-4963 affects spring module core. Severity is medium (CVSS 5.5). A vulnerability was found in Folio Spring Module Core up to 1.1.5. It has been rated as critical. Affected by this issue is the function dropSchema of the file tenant/src/main/java/org/folio/spring/tenant/hibernate/HibernateSchemaService.ja

Q: How urgent is CVE-2022-4963?

Priority 31/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2022-4963 is a medium-severity flaw (CVSS 5.5) affecting spring module core. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in Folio Spring Module Core up to 1.1.5. It has been rated as critical. Affected by this issue is the function dropSchema of the file tenant/src/main/java/org/folio/spring/tenant/hibernate/HibernateSchemaService.java of the component Schema Name Handler. The manipulation leads to sql injection. Upgrading to version 2.0.0 is able to address this issue. The name of the patch is d374a5f77e6b58e36f0e0e4419be18b95edcd7ff. It

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-89
Published	2024-03-21
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: folio

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-03-21 02:44 UTCPublished CVE record published
2026-06-17 05:22 UTCUpdated Record last modified

folio spring module core UPGRADE

Affected: < 2.0.0

Fixed in: 2.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy spring-module-core || rpm -q spring-module-core || spring-module-core --version

2. UPGRADE to 2.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-module-core

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-module-core

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-4963?

spring module core: upgrade to 2.0.0. Exact commands for each OS are on this page.

Is CVE-2022-4963 being exploited?

CVE-2022-4963 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-4963 affect?

CVE-2022-4963 affects spring module core. Severity is medium (CVSS 5.5). A vulnerability was found in Folio Spring Module Core up to 1.1.5. It has been rated as critical. Affected by this issue is the function dropSchema of the file tenant/src/main/java/org/folio/spring/tenant/hibernate/HibernateSchemaService.ja

How urgent is CVE-2022-4963?

Priority 31/100. No elevated risk signals yet.

Software pages

Java vulnerabilities

References

← Back to latest CVEs