CVE-2024-11922
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 · uneditedMissing input validation in certain features of the Web Client of Fortra's GoAnywhere prior to version 7.8.0 allows an attacker with permission to trigger emails to insert arbitrary HTML or JavaScript into an email.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in Fortra's GoAnywhere MFT Web Client. An authenticated attacker with permission to trigger emails can inject arbitrary HTML or JavaScript into email content due to missing input validation, potentially affecting users who view these emails.
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< 7.8.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.
-
Check GoAnywhere MFT versionLocate the installed version of GoAnywhere MFT in the administration interface under System > Summary or by checking the installation directory for version information filesAffected if The installed version is below 7.8.0
-
Verify Web Client is enabledCheck the GoAnywhere MFT administration console under Services > Web Server or similar settings to confirm the Web Client interface is activeAffected if The Web Client service is enabled and accessible to users
-
Confirm email feature accessReview user permissions in the administration console to determine which authenticated users or roles have permission to create or trigger email notificationsAffected if Any authenticated user role includes permission to trigger or compose emails through the Web Client
-
Inspect email logs for suspicious contentExamine GoAnywhere MFT email logs or audit trails in the admin console under Logs or Audit section, looking for any email records containing HTML tags, script elements, or JavaScript event handlersAffected if Email logs contain entries with unescaped HTML or script tags in subject, body, or recipient fields
The environment is affected if GoAnywhere MFT version is below 7.8.0 AND the Web Client with email functionality is enabled for authenticated users.
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 · scoped7.8.0
Upgrade GoAnywhere MFT to version 7.8.0 or later which contains the fix for this input validation vulnerability.
GoAnywhere MFT 7.8.0
- Back up the current GoAnywhere MFT installation and configuration
- Download GoAnywhere MFT version 7.8.0 or later from Fortra's official download portal
- Follow Fortra's documented upgrade procedure for your deployment type (container, installer, or manual)
- After upgrading, verify the email functionality works correctly and no XSS payloads execute in emails
- Confirm the version number reflects 7.8.0 or higher in the admin console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11922 — 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-11922 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