dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-12504

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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') vulnerability in Talent Software UNIS allows SQL Injection. This issue affects UNIS: before 42321.

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

SQL injection vulnerability in Talent Software UNIS allows attackers to inject malicious SQL commands through unsanitized input fields. The flaw exists due to improper neutralization of special elements in SQL queries, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationUpgrade UNIS to version 42321 or later. As an immediate control, validate and sanitize all user-supplied input before using it in SQL queries, and implement parameterized queries or prepared statements.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Talent Software UNIS installation
    Check for UNIS application files, services, or binaries on the system. Look for processes named 'unis' or directories containing 'unis' in the installation path.
    Affected if Talent Software UNIS is not present on the system.
  2. Identify installed UNIS version
    Locate version information in UNIS configuration files, about dialog, or executable metadata. Common locations: installation directory, version.txt, or run 'unis -v' if CLI is available.
    Affected if Version is lower than 42321 (e.g., 42320, 42200, 41000, etc.) or version cannot be determined.
  3. Verify SQL query handling exists
    Review application source code, configuration, or logs to confirm the UNIS application processes database queries. Check for SQL execution modules or database connection configurations.
    Affected if UNIS application uses database queries and processes user input through SQL operations.
  4. Inspect input field handling
    Examine UNIS web interface or application forms for input fields that interact with database queries. Test by submitting SQL syntax characters (', ;, --) in form fields and observe application response or logs.
    Affected if Application accepts user input that flows directly into SQL queries without visible sanitization or parameterization.

If Talent Software UNIS version is lower than 42321 and the application processes user-supplied input through SQL queries without parameterized handling, the environment is affected by CVE-2025-12504.

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 UNIS to version 42321 or later. As an immediate control, validate and sanitize all user-supplied input before using it in SQL queries, and implement parameterized queries or prepared statements.

Recommended fix Moderate confidence

UNIS version 42321 or later

  1. 1. Identify the current version of Talent Software UNIS installed in your environment
  2. 2. If the current version is before build 42321, plan for an upgrade
  3. 3. Perform a complete backup of the UNIS database before proceeding with any changes
  4. 4. Obtain the updated UNIS version 42321 or later from the vendor (Talent Software)
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Apply the upgrade to production systems following vendor documentation

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-12504 — 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-12504 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