dbcve.org
FortiportalApplication · Fortinet

CVE-2023-48791

HIGH · 8.8 CVSS v3.1 Published 2023-12-13
Fix available
A fix is available. Upgrade to after 7.0.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
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 arguments in the Schedule System Backup page field.

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 · high confidence

FortiPortal versions 7.2.0 and 7.0.6 and below contain a command injection vulnerability (CWE-77) in the Schedule System Backup page. A remote authenticated attacker with at least Read/Write permissions can execute unauthorized operating system commands by providing specially crafted arguments in the backup schedule field.

MitigationApply the vendor-supplied patch for FortiPortal to address the input validation vulnerability in the Schedule System Backup functionality. Until patched, consider restricting backup page permissions to minimum required users and implementing compensating network controls.

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
FortiportalApplication
Affected:>= 7.0.0, <= 7.0.6= 7.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 FortiPortal installation and version
    Access the FortiPortal web UI and navigate to the System Settings or About page to view the version number. Alternatively, check via CLI or API if available.
    Affected if The installed version is 7.0.0 through 7.0.6 inclusive, or exactly 7.2.0
  2. Confirm user access to Schedule System Backup
    Log into FortiPortal with the target account and navigate to System > System Administration > Schedule System Backup, or the equivalent backup settings page.
    Affected if The user account has Read/Write permissions to the Schedule System Backup functionality
  3. Verify backup schedule feature is enabled
    In the FortiPortal interface, check if the Schedule System Backup feature is configured or enabled in the backup settings.
    Affected if The backup schedule feature is accessible and can be configured by the authenticated user
  4. Review backup configuration for injection points
    Inspect the backup schedule field parameters using the web UI or by intercepting API requests when saving a backup schedule.
    Affected if The backup schedule field accepts user input without apparent input validation or sanitization

A user is affected if FortiPortal version is 7.0.0-7.0.6 or 7.2.0 AND the authenticated user has Read/Write access to the Schedule System Backup feature.

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 a release after 7.0.6
Interim mitigation

Apply the vendor-supplied patch for FortiPortal to address the input validation vulnerability in the Schedule System Backup functionality. Until patched, consider restricting backup page permissions to minimum required users and implementing compensating network controls.

Recommended fix High confidence

FortiPortal 7.0.7 or 7.2.1 (or latest stable release above 7.2.0)

  1. 1. Identify current FortiPortal version via the FortiPortal admin console or CLI
  2. 2. Download FortiPortal version 7.0.7 or 7.2.1 (or latest stable) from the Fortinet Support Portal at support.fortinet.com
  3. 3. Review FortiPortal upgrade documentation for your deployment type (hardware/virtual appliance)
  4. 4. Backup current FortiPortal configuration and verify backup integrity
  5. 5. Initiate the upgrade via FortiPortal admin interface or CLI command appropriate to your deployment
  6. 6. Monitor the upgrade process for completion
  7. 7. Verify the upgraded version matches the expected fixed version (7.0.7 or 7.2.1 or later)
  8. 8. Confirm the Schedule System Backup functionality works correctly
Caveat Review FortiPortal release notes for any configuration or feature changes between your current version and the target version before upgrading

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

Fix this in Fortiportal Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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