Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-26853 is a critical-severity Incorrect Authorization (CWE-863) vulnerability in Descor Infocad. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-25 (Reference Monitor) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-26853 is a critical vulnerability in DESCOR INFOCAD versions 3.5.1 and prior, stemming from a broken authorization schema as indicated by associated CWEs-863 (Incorrect Authorization) and CWE-862 (Missing Authorization). The issue received a perfect CVSS v3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), highlighting its severity due to network accessibility, low attack complexity, no required privileges or user interaction, and broad impacts across confidentiality, integrity, and availability with a changed scope. It was published on 2025-03-20.
Unauthenticated attackers can exploit this vulnerability remotely over the network with minimal effort, bypassing authorization controls to gain unauthorized access to the affected INFOCAD software. Successful exploitation enables high-impact outcomes, including complete compromise of confidentiality (e.g., data exposure), integrity (e.g., data manipulation), and availability (e.g., denial of service), potentially leading to full system control given the scope change.
Advisories point to mitigation via patching, with the vulnerability fixed in INFOCAD version 3.5.2.0 as detailed in the official changelog. Security practitioners should reference the DESCOR INFOCAD product page and the specific changelog entry on broken authorization schema for deployment guidance and verification.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-7149
Vulnerability Data
DESCOR INFOCAD 3.5.1 and before and fixed in v.3.5.2.0 has a broken authorization schema.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 10 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly requires correct enforcement of authorization decisions on every access request, structurally preventing incorrect checks.
AC-24 ensures access-control decisions are made and applied consistently, reducing the chance of an incorrect authorization result.
A reference monitor that is always invoked and tamper-proof forces every authorization decision through a verified, correct path.
Least-privilege assignments shrink the set of authorizations that must be checked correctly, limiting exposure to flawed checks.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Explicitly requires defining, enforcing, and reviewing authorizations and least privilege, directly preventing missing authorization checks.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring authentication and credentials before any access occurs eliminates the absence of authorization checks that would otherwise allow an unauthenticated actor to reach protected resources.
Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.
Enforcing policy-driven approval and role-change reviews stops incorrect or stale authorization decisions from remaining in effect after job changes or terminations.
Segregating the approval of access rights from their implementation provides an independent check that reduces the impact of missing authorization checks in the resulting system configuration.
By requiring competent outsiders to verify that every function enforces the need-to-know principle, the control lowers the likelihood that missing authorization checks persist undetected.
Defining authorization responsibilities and reviewing risk-treatment progress throughout the project lifecycle catches missing authorization checks before the system is deployed.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248581 OL 8 must require users to provide a password for privilege escalation. prevents CWE-862, CWE-863
- V-252656 The OL 8 operating system must not be configured to bypass password requirements for privilege escalation. prevents CWE-862, CWE-863
RHEL 7 (3 rules)
- V-251704 The Red Hat Enterprise Linux operating system must not be configured to bypass password requirements for privilege escalation. prevents CWE-862
- V-204429 The Red Hat Enterprise Linux operating system must be configured so that users must provide a password for privilege escalation. prevents CWE-862
- V-204430 The Red Hat Enterprise Linux operating system must be configured so that users must re-authenticate for privilege escalation. prevents CWE-863
RHEL 8 (1 rule)
- V-251712 The RHEL 8 operating system must not be configured to bypass password requirements for privilege escalation. prevents CWE-863