CVE-2026-0972
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 · uneditedHTML injection is possible in system generated emails in Fortra's GoAnywhere MFT prior to 7.10.0. Note: The title, details, and description of this CVE were corrected post-publishing.
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 confidenceHTML injection vulnerability in GoAnywhere MFT's system-generated emails allows attackers to inject malicious HTML content into email notifications. This could enable phishing attacks, credential theft, or distribution of malicious content through trusted MFT system 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.10.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 versionLog into the GoAnywhere Admin Console and navigate to the 'About' or 'System Information' page to view the installed version. Alternatively, check the installation directory for a version file or review startup logs that typically display the version number on service startup.Affected if The displayed version number is less than 7.10.0 (for example, 7.9.x, 7.8.x, or earlier)
-
Verify email notification configurationIn the GoAnywhere Admin Console, navigate to the 'System Settings' or 'Email Settings' section under the Configuration menu. Check if SMTP/email notifications are enabled and configured for system alerts, user notifications, or transfer notifications.Affected if Email notifications are enabled and configured (the vulnerability affects system-generated emails, so this must be active for exploitation)
-
Review email template configurationAccess the 'Email Templates' or 'Notifications' section in the Admin Console. Examine the settings for system-generated emails such as user welcome emails, password reset notifications, transfer completion alerts, and administrative alerts.Affected if Custom email templates are in use or email notifications are configured to send HTML-formatted content (the injection point is in system-generated email content)
-
Confirm active user accounts and email deliveryIn the Admin Console, check the 'Users' or 'Activity' log to confirm that the system is actively sending email notifications to users. Review recent email activity or notification logs if available.Affected if The system has active users and is delivering email notifications (indicating the attack vector is viable)
The environment is affected if GoAnywhere MFT version is below 7.10.0 AND email notifications are enabled, allowing attackers to inject malicious HTML into system-generated emails.
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.10.0
Upgrade GoAnywhere MFT to version 7.10.0 or later to patch the HTML injection vulnerability in system-generated emails.
7.10.0
- Download GoAnywhere MFT version 7.10.0 from the official Fortra customer portal or authorized distribution channel
- Review the GoAnywhere MFT 7.10.0 release notes and upgrade instructions provided by Fortra
- Create a full backup of the current GoAnywhere MFT installation including configuration files and database
- Stop the GoAnywhere MFT service before beginning the upgrade process
- Install version 7.10.0 following the standard upgrade procedure documented by Fortra
- After installation, verify the upgrade was successful by checking the version number in the admin console
- Start the GoAnywhere MFT service and confirm all services are running properly
- Test system-generated email functionality to confirm the HTML injection vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0972 — 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-2026-0972 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