FortiwlmApplication · Fortinet
CVE-2023-42783
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 · uneditedA relative path traversal in Fortinet FortiWLM version 8.6.0 through 8.6.5 and 8.5.0 through 8.5.4 and 8.4.2 through 8.4.0 and 8.3.2 through 8.3.0 and 8.2.2 allows attacker to read arbitrary files via crafted http requests.
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 confidenceA relative path traversal vulnerability in Fortinet FortiWLM allows unauthenticated attackers to read arbitrary files on the filesystem by crafting malicious HTTP requests with path traversal sequences (e.g., ../../../etc/passwd). The vulnerability affects versions 8.2.2 through 8.6.5 across multiple branches and stems from insufficient input validation on HTTP request parameters used in file access operations.
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
FortiwlmApplication
>= 8.5.0, <= 8.5.4>= 8.6.0, <= 8.6.6= 8.2.2= 8.3.0= 8.3.1= 8.3.2= 8.4.0= 8.4.1= 8.4.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiWLM versionLog into the FortiWLM management interface or run the command 'fwmanager -v' or check the system information page to obtain the installed firmware version.Affected if The installed version falls within these ranges: 8.2.2; 8.3.0-8.3.2; 8.4.0-8.4.2; 8.5.0-8.5.4; 8.6.0-8.6.6.
-
Confirm web interface is accessibleVerify that the FortiWLM web interface (HTTPS/HTTP ports 80/443 or custom management ports) is listening and reachable from network locations. Check with 'netstat -an | grep -E "80|443"' or review firewall rules.Affected if The web interface is exposed to untrusted networks or the internet.
-
Review HTTP access logs for path traversal attemptsExamine FortiWLM web server access logs for requests containing '../' sequences, such as '../../../etc/passwd' or similar path traversal patterns in URL parameters.Affected if Logs show any HTTP requests with '../' sequences targeting sensitive system files.
-
Check for unauthorized file accessCompare recent file access timestamps on sensitive system files (/etc/passwd, /etc/shadow, configuration directories) against known legitimate administrative activities.Affected if File access patterns do not correspond to known administrative actions or show access from unexpected sources.
You are affected if FortiWLM version is within 8.2.2 through 8.6.6 AND the web management interface is accessible from a network where untrusted users can send HTTP requests.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor-supplied patch by upgrading FortiWLM to a patched version beyond 8.6.5. As a temporary compensating control, restrict access to the FortiWLM web interface to trusted networks only via firewall rules or WAF filtering.
FortiWLM 8.6.7+, 8.5.5+, 8.4.3+, 8.3.3+, or 8.2.3+ (choose the latest available in your branch)
- 1. Identify the current FortiWLM version by accessing the device CLI or web interface
- 2. Determine the current major version branch (8.2.x, 8.3.x, 8.5.x, or 8.6.x)
- 3. For branch 8.6.x: Upgrade to FortiWLM version 8.6.7 or later
- 4. For branch 8.5.x: Upgrade to FortiWLM version 8.5.5 or later
- 5. For branch 8.4.x: Upgrade to FortiWLM version 8.4.3 or later
- 6. For branch 8.3.x: Upgrade to FortiWLM version 8.3.3 or later
- 7. For branch 8.2.x: Upgrade to FortiWLM version 8.2.3 or later
- 8. After upgrade, verify the installation and test that the web interface is functional
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiwlm
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42783 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-42783 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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