Stirling-PDF from 2.13.2 through 3.2.0 contains an incomplete denylist in DatabaseService.validateSqlContent() that allows administrators to bypass H2 import restrictions using CREATE OR REPLACE ALIAS. Authenticated administrators can upload a crafted SQL backup to the import-database endpoint, where RUNSCRIPT defines H2 Java function aliases and restores Java-method execution.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 6
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-20 18:06
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-20 20:06
- StatusReceived → PublishedNVD modified 2026-10-20 18:06
- StatusPublished → ReceivedNVD modified 2026-10-20 19:17
- StatusReceived → PublishedNVD modified 2026-10-20 15:40
- First seenCVSS 8.6NVD modified 2026-10-20 16:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://abraxaslabs.tech/research/stirling-h2-import-leftover
- https://abraxaslabs.tech/research/stirling-pdf-3.2.0-leftovers
- https://github.com/Stirling-Tools/Stirling-PDF/blob/v3.2.0/app/proprietary/src/main/java/stirling/software/proprietary/security/service/DatabaseService.java
- https://github.com/abraxas/stirling-h2-import-leftover
- https://www.vulncheck.com/advisories/stirling-pdf-2.13.2-through-3.2.0-h2-sql-denylist-bypass-via-import-database