dbcve.org
FortiproxyApplication · Fortinet

CVE-2023-29183

MEDIUM · 5.4 CVSS v3.1 Published 2023-09-13
Fix available
A fix is available. Upgrade to 6.2.15 / 6.4.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 input during web page generation ('Cross-site Scripting') vulnerability [CWE-79] in FortiProxy 7.2.0 through 7.2.4, 7.0.0 through 7.0.10 and FortiOS 7.2.0 through 7.2.4, 7.0.0 through 7.0.11, 6.4.0 through 6.4.12, 6.2.0 through 6.2.14 GUI may allow an authenticated attacker to trigger malicious JavaScript code execution via crafted guest management setting.

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

A stored cross-site scripting (XSS) vulnerability in FortiProxy and FortiOS GUI allows authenticated attackers to execute malicious JavaScript code via crafted guest management settings. The vulnerability exists in multiple product versions spanning FortiOS 6.2 through 7.2 and FortiProxy 7.0 through 7.2.

MitigationUpgrade to FortiOS 7.2.5+, 7.0.12+, 6.4.13+, 6.2.15+ or FortiProxy 7.2.5+, 7.0.11+ as specified in the Fortinet security advisory. Alternatively, restrict GUI access to trusted users only.

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
FortiproxyApplication
Affected:>= 7.0.0, < 7.0.11>= 7.2.0, < 7.2.5
FortiosOperating system
Affected:>= 6.2.0, < 6.2.15>= 6.4.0, < 6.4.13>= 7.0.0, < 7.0.12>= 7.2.0, < 7.2.5

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 FortiOS or FortiProxy version
    Run 'get system status' in the CLI to retrieve the firmware version
    Affected if The installed version is FortiOS 6.2.0 through 6.2.14, 6.4.0 through 6.4.12, 7.0.0 through 7.0.11, or 7.2.0 through 7.2.4; OR FortiProxy 7.0.0 through 7.0.10 or 7.2.0 through 7.2.4
  2. Confirm GUI administrative access is enabled
    Run 'get system interface' in the CLI and look for HTTP or HTTPS services on any interface, or check System > Administration > Administrators in the GUI
    Affected if HTTP or HTTPS management access is enabled on any interface, exposing the GUI to users
  3. Check if guest management feature is accessible
    Navigate to User & Authentication > Guest Management in the GUI, or run 'get guest' in the CLI to list guest user configurations
    Affected if Guest management settings can be created or modified by authenticated users

The environment is affected if the device runs an affected FortiOS or FortiProxy version with GUI access enabled and guest management features are available to authenticated users.

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 6.2.15 / 6.4.13 / 7.0.11 or later
Fixed in 6.2.156.4.137.0.11
Interim mitigation

Upgrade to FortiOS 7.2.5+, 7.0.12+, 6.4.13+, 6.2.15+ or FortiProxy 7.2.5+, 7.0.11+ as specified in the Fortinet security advisory. Alternatively, restrict GUI access to trusted users only.

Recommended fix High confidence

FortiOS 6.2.15+, 6.4.13+, 7.0.12+, 7.2.5+ | FortiProxy 7.0.11+, 7.2.5+

  1. 1. Identify the currently installed FortiOS or FortiProxy version by running: get system status
  2. 2. Determine the appropriate upgrade path based on current version branch (6.2.x, 6.4.x, 7.0.x, or 7.2.x)
  3. 3. Download the corresponding firmware upgrade from Fortinet Customer Support portal: https://support.fortinet.com/
  4. 4. Upload the firmware to the Fortinet device via Web UI (System > Firmware) or CLI: execute firmware upgrade <filepath>
  5. 5. Reboot the device after upgrade completes: execute reboot
  6. 6. Verify the upgrade was successful and confirm new version: get system status
  7. 7. Test the guest management functionality to confirm the XSS fix is working properly
Caveat Standard firmware upgrade precautions apply - ensure backups of configuration are taken before upgrading, and plan for brief downtime during the upgrade and reboot process

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
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,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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