CVE-2026-25088: An improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Fo...
An improper neutralization of special elements used in an sql command ('sql injection') vulnerability in Fortinet FortiNDR 7.6.0 through 7.6.2, FortiNDR 7.4.0 through 7.4.9, FortiNDR 7.2 all versions, FortiNDR 7.1 all versions, FortiNDR 7.0 all versions may allow an authenticated attacker to execute unauthorized code or commands via specifically crafted HTTP requests.
Security readout for executives and security teams
Plain-English summary
CVE-2026-25088 is an authenticated SQL injection issue in Fortinet FortiNDR. A logged-in attacker could send crafted HTTP requests that may lead to unauthorized code or command execution. The business risk is most relevant where FortiNDR is reachable by many users or exposed beyond tightly controlled administration networks.
Executive priority
Treat as a scheduled but important security update. Escalate priority if FortiNDR is internet-reachable, broadly accessible internally, or used in sensitive monitoring environments where command execution could undermine trust in detection operations.
Technical view
The vulnerability is CWE-89 in FortiNDR 7.6.0-7.6.2, 7.4.0-7.4.9, and all 7.2, 7.1, and 7.0 releases. CVSS 3.1 is 5.1 with network access, low complexity, low privileges, no user interaction, and limited confidentiality and integrity impact.
Likely exposure
Exposure is limited to organizations running affected FortiNDR versions, especially systems with HTTP management or application interfaces reachable by authenticated users. The source bundle marks other versions as unaffected by default but does not provide fixed-version details.
Exploitation context
The source bundle does not establish active exploitation; KEV is false. Exploitation requires authentication and crafted HTTP requests. Public evidence in the bundle supports proof-of-concept maturity via CVSS E:P, but no exploit procedure or real-world activity is cited.
Researcher notes
Evidence is strongest for affected ranges, vulnerability class, prerequisites, and CVSS. The bundle does not include fixed release numbers, workarounds, affected endpoints, or confirmed exploitation. Avoid assuming unauthenticated impact or internet-scale exploitation without additional vendor or KEV evidence.
Mitigation direction
Check Fortinet PSIRT FG-IR-26-134 for official fixed releases and upgrade guidance.
Prioritize remediation for FortiNDR exposed outside restricted management networks.
Limit FortiNDR access to trusted administrators and controlled network paths.
Review accounts with FortiNDR access and remove unnecessary privileges.
Monitor FortiNDR HTTP and authentication logs for suspicious authenticated activity.
Validation and detection
Inventory all FortiNDR appliances and record exact software versions.
Compare versions against affected 7.6, 7.4, 7.2, 7.1, and 7.0 ranges.
Confirm whether FortiNDR interfaces are reachable from untrusted networks.
Review recent authenticated HTTP activity for unusual requests or account behavior.
After remediation, verify the installed version is outside the affected range.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.