Security Resilience

CVE-2023-48791

RCE in Fortinet Fortiportal 7.0.0 – 7.0.6

Published
13 December 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.013 69th percentile
Risk Priority 68 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-48791 is a high-severity Command Injection (CWE-77) vulnerability in Fortinet Fortiportal. Its CVSS base score is 8.8 (High).

Operationally, ranked in the top 31% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

An improper neutralization of special elements used in a command ('Command Injection') vulnerability [CWE-77] in FortiPortal version 7.2.0, version 7.0.6 and below may allow a remote authenticated attacker with at least R/W permission to execute unauthorized commands via specifically crafted…

more

arguments in the Schedule System Backup page field.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-35278Same product: Fortinet Fortiportal
CVE-2023-47543Same product: Fortinet Fortiportal
CVE-2024-31495Same product: Fortinet Fortiportal
CVE-2023-48789Same product: Fortinet Fortiportal
CVE-2023-48783Same product: Fortinet Fortiportal
CVE-2024-21759Same product: Fortinet Fortiportal
CVE-2023-46712Same product: Fortinet Fortiportal
CVE-2024-52967Same product: Fortinet Fortiportal
CVE-2025-24470Same product: Fortinet Fortiportal
CVE-2024-45329Same product: Fortinet Fortiportal

Affected Assets

fortinet
fortiportal
7.2.0 · 7.0.0 — 7.0.6

Mitigating Controls

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.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References