FortisoarApplication · Fortinet
CVE-2024-48893
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 · uneditedAn improper neutralization of input during web page generation vulnerability [CWE-79] in FortiSOAR 7.3.0 through 7.3.3, 7.2.1 through 7.2.2 may allow an authenticated attacker to perform a stored cross site scripting (XSS) attack via the creation of malicious playbook.
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 confidenceFortiSOAR versions 7.3.0-7.3.3 and 7.2.1-7.2.2 contain a stored cross-site scripting (XSS) vulnerability (CWE-79) in the playbook creation functionality. An authenticated attacker can inject malicious JavaScript payload through playbook fields which is then stored and executed when other users view the affected playbook, allowing session hijacking or data theft.
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
FortisoarApplication
>= 7.2.1, <= 7.3.3CVSS 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 FortiSOAR versionAccess the FortiSOAR administration UI and navigate to the System Settings or About section to view the installed version. Alternatively, use the CLI command 'fortisoar --version' or check the UI footer for version information.Affected if The installed version falls within 7.2.1-7.2.2 or 7.3.0-7.3.3.
-
Verify playbook module is accessibleConfirm that the Playbooks module is enabled and accessible in the FortiSOAR UI. Navigate to the Playbooks section from the main menu to verify the module is present and operational.Affected if The Playbooks module is active and users have access to create or view playbooks.
-
Check user permissions for playbook creationIn FortiSOAR, go to Administration > Roles or Users to review role permissions. Determine whether the current user or any user role has 'Create' or 'Edit' permissions on the Playbooks module.Affected if Users possess playbook creation or editing permissions, allowing them to inject payloads into playbook fields.
-
Inspect existing playbooks for suspicious contentNavigate to the Playbooks list view and review playbook names, descriptions, and field values for unusual characters such as <script>, javascript:, or encoded payloads. Use search or filter if available to identify potentially malicious entries.Affected if Any playbooks contain JavaScript code or HTML tags in their fields that could indicate exploitation.
A user is affected if their FortiSOAR version is between 7.2.1-7.2.2 or 7.3.0-7.3.3 and the Playbooks module is accessible to authenticated users with creation permissions.
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.
From vendor dataUpgrade FortiSOAR to version 7.3.4 or 7.2.3 or later per vendor advisory. As a compensating control, restrict playbook creation permissions to trusted users and implement Content Security Policy headers.
Fix this in Fortisoar
Scoped from the published advisory
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48893 — 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-2024-48893 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