CVE-2025-26853
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 · uneditedDESCOR INFOCAD 3.5.1 and before and fixed in v.3.5.2.0 has a broken authorization schema.
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 · low confidenceDESCOR INFOCAD versions 3.5.1 and prior contain a broken authorization schema vulnerability that allows unauthorized users to bypass access controls, leading to full system compromise. The critical 9.8 CVSS score indicates this flaw is likely exploitable remotely without authentication.
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< 3.5.2.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Descor Infocad versionLocate the installed version of Descor Infocad in the application, typically found in the software's About dialog, installation directory metadata, or version information file provided with the productAffected if The installed version is 3.5.1 or any version number lower than 3.5.2.0
-
Confirm version falls within vulnerable rangeCompare your identified version against the affected range: any version before 3.5.2.0 is vulnerableAffected if The version is 3.5.1 or earlier, or any build prior to 3.5.2.0
-
Assess application network exposureDetermine if the Descor Infocad application is accessible over the network or exposed via web interfaces, APIs, or remote services that could be reached by unauthenticated attackersAffected if The application is network-accessible and runs a version低于3.5.2.0, enabling potential unauthenticated exploitation
If the installed Descor Infocad version is 3.5.1 or any version before 3.5.2.0 and the application is network-accessible, the environment is likely affected by this broken authorization vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.5.2.0
Upgrade to DESCOR INFOCAD v.3.5.2.0 or later. Until patched, restrict network exposure and monitor for unauthorized access attempts.
3.5.2.0
- 1. Backup the current Infocad installation and all associated data
- 2. Download Infocad version 3.5.2.0 from the official vendor source (www.descor.com or www.infocadfm.com)
- 3. Uninstall or deactivate the current version (3.5.1 or earlier)
- 4. Install version 3.5.2.0 following the vendor's installation instructions
- 5. Verify the authorization schema is functioning correctly after upgrade
- 6. Test that user role-based access controls are properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26853 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26853 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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