dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10968

HIGH · 8.8 CVSS v3.1 Published 2025-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), CWE - 564 - SQL Injection: Hibernate vulnerability in GG Soft Software Services Inc. PaperWork allows Blind SQL Injection, SQL Injection. This issue affects PaperWork: from 6.1.0.9390 before 6.1.0.9398.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a SQL Injection vulnerability in PaperWork (versions 6.1.0.9390 to before 6.1.0.9398) by GG Soft Software Services Inc. The vulnerability is specifically a Hibernate-based SQL injection, likely caused by unsanitized user input being used in Hibernate queries without proper parameterization. Both blind and standard SQL injection variants are present, allowing attackers to manipulate database queries and potentially exfiltrate sensitive data.

MitigationUpgrade PaperWork to version 6.1.0.9398 or later. If immediate patching is not possible, audit all Hibernate query implementations for proper input parameterization and implement input validation as a compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed PaperWork version
    Locate the PaperWork application version number in the application header, about page, or configuration files (typically in installation directory or version manifest)
    Affected if version is 6.1.0.9390 through 6.1.0.9397 (versions before 6.1.0.9398)
  2. Verify Hibernate is in use
    Inspect the application's library directory for Hibernate JAR files (hibernate-core, hibernate-entitymanager, etc.) or check configuration files (hibernate.cfg.xml, persistence.xml) for Hibernate settings
    Affected if Hibernate ORM framework is present in the application stack
  3. Locate custom Hibernate query implementations
    Search source code or decompiled classes for HQL/JPQL queries built using string concatenation rather than parameterized queries (look for session.createQuery() or session.createSQLQuery() with concatenated strings containing user-supplied values)
    Affected if custom Hibernate queries exist that construct query strings using unsanitized input
  4. Review user input pathways into database queries
    Examine controller/service layer code that passes request parameters, form inputs, or URL parameters into Hibernate query methods without using parameterized bindings (PreparedStatement parameters or setParameter/setString methods)
    Affected if user-controlled input flows directly into Hibernate query construction without parameter binding
  5. Test for SQL injection via HTTP endpoints
    Use a web vulnerability scanner or manually inject SQL meta-characters (single quotes, UNION SELECT, boolean-based payloads) into search fields, filters, or parameters that interact with the database through Hibernate
    Affected if application responds with database errors, unusual data, or timing differences indicating SQL injection is possible

If PaperWork version is 6.1.0.9390 through 6.1.0.9397 AND the application uses Hibernate with query implementations that incorporate user input without proper parameterization, the environment is likely affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade PaperWork to version 6.1.0.9398 or later. If immediate patching is not possible, audit all Hibernate query implementations for proper input parameterization and implement input validation as a compensating control.

Recommended fix High confidence

PaperWork 6.1.0.9398

  1. 1. Identify the current version of PaperWork installation by checking the application metadata or system information
  2. 2. Create a complete backup of the PaperWork database and all application data before proceeding with the upgrade
  3. 3. Download PaperWork version 6.1.0.9398 or a later stable release from the vendor's official distribution channel
  4. 4. Stop the PaperWork application services to ensure a clean upgrade process
  5. 5. Install the upgraded version (6.1.0.9398 or later) following the vendor's standard upgrade procedure
  6. 6. Restart the PaperWork application services
  7. 7. Verify the upgrade was successful by confirming the new version number in the system
  8. 8. Test that the application functions normally and that the SQL injection vulnerability is no longer exploitable

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10968 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10968 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data