Safeguard
Vulnerability Analysis•

CVE-2022-4963: Medium SQL Injection in FOLIO Spring Module Core

CVE-2022-4963 is a medium SQL injection flaw in FOLIO Spring Module Core up to 1.1.5, scored 5.5. Upgrade to version 2.0.0 or later to fix it.

Safeguard Security Team
4 min read

CVE-2022-4963 is a medium severity SQL injection flaw in FOLIO Spring Module Core up to version 1.1.5, scored 5.5 by NVD. The dropSchema function builds SQL from a schema name that was not validated. The fix is version 2.0.0, so upgrade the library to that or later.

What's affected

The record says FOLIO Spring Module Core up to 1.1.5 is affected, in the function dropSchema of HibernateSchemaService.java, part of the schema name handler in the tenant module. Manipulating the schema name leads to SQL injection. The record gives the identifier VDB-257516 and the vector CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, which needs adjacent network access and a low privilege account.

The record says upgrading to version 2.0.0 addresses the issue and names the patch commit d374a5f. The project's pull request 39, titled for schema name SQL injection, was merged on December 1, 2022. The commit adds a check that a schema name matches only letters, digits and underscores, and changes the schemaExists query to use a bound parameter instead of a formatted string.

The record and the project's own change agree on the cause and the fix. Note that the CVE was published in March 2024, more than a year after the merge, so projects that scan advisories only may have learned about it late.

Weakness class: CWE-89.

How to check if you're exposed

The library is pulled in as a dependency, so list it from your build. For Maven projects:

mvn dependency:tree | grep -i folio

Look for spring-module-core, or the artifacts your FOLIO modules use that depend on it, and read the version. Anything up to 1.1.5 is in range. For Gradle, run gradle dependencies and search the output the same way.

Also check for transitive use. Modules built on the FOLIO Spring libraries may carry the dependency without naming it, so check each module's resolved tree.

What to do now

  1. Run a dependency report on every FOLIO module you build or deploy.
  2. Upgrade spring-module-core to 2.0.0 or later and run the module's tests.
  3. Review code that builds SQL from tenant or schema names, and use validation and bound parameters.
  4. Restrict who can create or remove tenants, since the affected path is tenant administration.
  5. Rebuild and redeploy images, then confirm the new version in the final artifact.

Why it matters

Schema names cannot be passed as query parameters in most databases, so code that creates or drops a schema often formats the name into the SQL string. When the name comes from a tenant identifier that someone else controls, the string can carry extra SQL. The record files it as CWE-89, SQL injection.

The project's fix does the two things that matter. It validates the name against a strict pattern before use, and it moves the existence check to a bound parameter. That pairing is what to look for in reviews of any code that has to put identifiers into SQL.

Multi tenant platforms make the stakes higher. A flaw in schema handling is a flaw in the wall between tenants, even when the score is only 5.5, and the adjacent network requirement narrows who can reach it.

This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.

Safeguard's free in-browser dependency scan at gold.safeguard.sh/scan reads your manifests and lock files and shows which known CVEs apply to the packages you ship. Paste in your pom.xml or lock file to see whether a vulnerable version of this library is present.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Which version fixes CVE-2022-4963?

The record says upgrading to 2.0.0 addresses it, and the project merged its fix in pull request 39 on December 1, 2022.

What does the fix change?

Per the commit, schema names are checked against a pattern of letters, digits and underscores, and the schemaExists query uses a prepared statement.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.