dbcve.org
Firewall FirmwareOperating system · Sophos

CVE-2025-7624

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-21
Fix available
A fix is available. Upgrade to 21.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An SQL injection vulnerability in the legacy (transparent) SMTP proxy of Sophos Firewall versions older than 21.0 MR2 (21.0.2) can lead to remote code execution, if a quarantining policy is active for Email and SFOS was upgraded from a version older than 21.0 GA.

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 confidence

SQL injection vulnerability in the legacy (transparent) SMTP proxy of Sophos Firewall allows remote code execution. Exploitation requires both a quarantining policy to be active for Email and the appliance to have been upgraded from a version older than 21.0 GA.

MitigationUpgrade Sophos Firewall to version 21.0 MR2 (21.0.2) or later. If immediate upgrade is not feasible, disable the legacy SMTP proxy or remove the quarantining policy as a temporary mitigation.

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
Firewall FirmwareOperating system
Affected:< 21.0.2

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Sophos Firewall firmware version
    Access the firewall's web admin console and navigate to System > Overview, or run 'version' command in CLI to retrieve the current firmware version number
    Affected if The installed version is earlier than 21.0.2 (21.0 MR2)
  2. Confirm legacy (transparent) SMTP proxy is enabled
    Navigate to Email > SMTP Proxy in the web admin console, or check the SMTP proxy settings via CLI command 'smtp-proxy' to see if the legacy transparent proxy is active
    Affected if The legacy SMTP proxy mode is enabled and running
  3. Verify Email quarantining policy is active
    Navigate to Email > Quarantine > Policies in the web admin console, or inspect the quarantining configuration to determine if any quarantine policy is applied to SMTP traffic
    Affected if An Email quarantining policy is configured and actively applied to SMTP traffic
  4. Review firmware upgrade history
    Check System > Backup & Firmware > Upgrade History in the web admin console, or use the CLI command 'upgrade history' to identify the original firmware version before any upgrades
    Affected if The firewall was upgraded from a version older than 21.0 GA (21.0.0), meaning the original version prior to the last firmware installation was pre-21.0 GA

A system is affected if it runs firmware below 21.0.2 AND has the legacy SMTP proxy enabled with an active Email quarantining policy AND was upgraded from a pre-21.0 GA version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 21.0.2 or later
Fixed in 21.0.2
Interim mitigation

Upgrade Sophos Firewall to version 21.0 MR2 (21.0.2) or later. If immediate upgrade is not feasible, disable the legacy SMTP proxy or remove the quarantining policy as a temporary mitigation.

Recommended fix High confidence

21.0.2 (21.0 MR2) or later

  1. 1. Backup the current Sophos Firewall configuration via the web admin console (Backup & Restore > Create Backup)
  2. 2. Download the fixed firmware version 21.0.2 (21.0 MR2) or later from the Sophos download portal at www.sophos.com
  3. 3. Navigate to Backup & Restore > Upload Firmware in the web admin console
  4. 4. Upload the firmware file and initiate the upgrade process
  5. 5. After upgrade completes, verify the firmware version shows 21.0.2 or higher under System > Licenses
  6. 6. Confirm the SMTP proxy settings are functioning correctly and the quarantining policy is active
Caveat Standard Sophos firmware upgrade considerations apply - ensure configuration backup before upgrading and test in staging if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firewall Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7624 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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