FortiedrApplication · Fortinet
CVE-2022-29057
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 improper neutralization of input during web page generation ('cross-site scripting') in Fortinet FortiEDR version 5.1.0, 5.0.0 through 5.0.3 Patch 6 and 4.0.0 allows a remote authenticated attacker to perform a reflected cross site scripting attack (XSS) by injecting malicious payload into the Management Console via various endpoints.
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 · moderate confidenceFortiEDR versions 5.1.0, 5.0.0-5.0.3 Patch 6, and 4.0.0 contain a reflected cross-site scripting (XSS) vulnerability in the Management Console. An authenticated remote attacker can inject malicious JavaScript payloads through various endpoints, which are reflected back without proper input sanitization, allowing execution in the context of other users' sessions.
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
FortiedrApplication
>= 5.0.0, < 5.0.3= 4.0.0= 5.0.3= 5.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the FortiEDR versionAccess the FortiEDR Management Console and navigate to the Settings or About section to find the installed version number. Alternatively, check the system documentation or use the FortiEDR CLI if available to retrieve the version.Affected if The installed version is 4.0.0, 5.0.0, 5.0.1, 5.0.2, 5.0.3, or 5.1.0 (any version from 4.0.0 through 5.1.0, excluding any versions not listed in the affected range).
-
Confirm Management Console accessVerify that remote access to the FortiEDR Management Console is enabled and reachable from network locations where untrusted users could potentially send requests.Affected if The Management Console is exposed to network access beyond trusted internal users without additional authentication controls.
-
Check for existing XSS indicatorsReview web server logs and FortiEDR event logs for any suspicious JavaScript injection patterns or unexpected script tags in request parameters that might indicate exploitation attempts.Affected if Log analysis reveals reflected parameters containing script tags or JavaScript event handlers in recent request logs targeting the console.
You are affected if your FortiEDR version falls within 4.0.0 through 5.1.0 and the Management Console is accessible to authenticated users who could inject malicious scripts through unsanitized input fields.
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 · scoped5.0.3
Apply the vendor-supplied patch for FortiEDR (contact Fortinet support for the fixed version). Implement output encoding and input validation on affected endpoints as a defense-in-depth measure pending the patch.
FortiEDR 5.0.3 Patch 6 or later / FortiEDR 5.2.0 or later (for 5.1.0 users)
- 1. Identify the current FortiEDR version installed in your environment
- 2. For FortiEDR 4.0.0: upgrade to version 5.0.3 Patch 6 or later
- 3. For FortiEDR 5.0.0 through 5.0.3: upgrade to version 5.0.3 Patch 6 or later
- 4. For FortiEDR 5.1.0: upgrade to version 5.2.0 or later (the next stable release)
- 5. After upgrade, verify the Management Console is accessible and functioning correctly
- 6. Confirm the XSS vulnerability is resolved by testing that injected scripts are no longer executed in the console endpoints
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiedr
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29057 — 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-2022-29057 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