dbcve.org
InfocadApplication · Descor

CVE-2025-26852

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-20
Fix available
A fix is available. Upgrade to 3.5.2.0 or later.
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
DESCOR INFOCAD 3.5.1 and before and fixed in v.3.5.2.0 allows SQL Injection.

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 DESCOR INFOCAD version 3.5.1 and prior allows attackers to inject malicious SQL queries, potentially compromising the database, gaining unauthorized access, or exfiltrating sensitive data. The fix is available in version 3.5.2.0.

MitigationUpgrade DESCOR INFOCAD to version 3.5.2.0 or later to remediate the SQL injection vulnerability. If immediate upgrade is not possible, implement input validation and parameterized queries as an interim control.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
InfocadApplication
Affected:< 3.5.2.0

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. Identify installed DESCOR INFOCAD version
    Locate the application through the Start Menu, check its About/Help dialog, or examine the program's main executable file properties for version information. If installed as a service or web application, check the installation directory for version manifests or readme files.
    Affected if The displayed version is 3.5.1 or prior (any version below 3.5.2.0)
  2. Verify version from installation files
    If the application was installed via an installer package, check the original installer filename or any installation logs for the embedded version number.
    Affected if The installer or log shows version 3.5.1 or lower
  3. Check application configuration files
    Examine the application configuration directory for any version.txt, manifest, or XML config files that explicitly state the software version.
    Affected if The configuration files indicate a version below 3.5.2.0
  4. Confirm application is running and accessible
    Determine if the DESCOR INFOCAD web interface or service is currently active and accessible to users or external systems, as the SQL injection is only exploitable when the application is running.
    Affected if The application is running AND the version is below 3.5.2.0

You are affected if the installed DESCOR INFOCAD version is 3.5.1 or any prior version (anything below 3.5.2.0) and the application is operational.

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
Upgrade available Upgrade to 3.5.2.0 or later
Fixed in 3.5.2.0
Interim mitigation

Upgrade DESCOR INFOCAD to version 3.5.2.0 or later to remediate the SQL injection vulnerability. If immediate upgrade is not possible, implement input validation and parameterized queries as an interim control.

Recommended fix High confidence

3.5.2.0

  1. Identify the currently installed version of DESCOR INFOCAD by checking the application or system information
  2. Create a complete backup of the current Infocad installation including all configuration files and databases
  3. Download DESCOR INFOCAD version 3.5.2.0 from the official vendor sources (descor.com or infocadfm.com)
  4. Stop the Infocad service or application to prevent active connections during upgrade
  5. Install version 3.5.2.0 following the vendor's standard upgrade procedure
  6. Start the Infocad service and verify the application runs without errors
  7. Confirm the version has been updated to 3.5.2.0

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

Fix this in Infocad Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26852 — 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-26852 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