CVE-2021-36807
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 authenticated user could potentially execute code via an SQLi vulnerability in the user portal of SG UTM before version 9.708 MR8.
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 confidenceAn authenticated SQL injection vulnerability exists in the user portal of Sophos SG UTM versions prior to 9.708 MR8, allowing authenticated users to inject malicious SQL queries that could lead to arbitrary code execution on the affected system.
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< 9.708CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Sophos SG UTM versionLog into the Sophos UTM web admin interface and navigate to System > Administration > System Settings > Version or use the command line 'version' to retrieve the installed firmware version.Affected if The installed version is lower than 9.708 MR8 (i.e., any version < 9.708).
-
Confirm Up2date subscription statusIn the web admin interface, go to System > Licensing > Up2date to verify the Up2date version and subscription status.Affected if The Up2date version shown is below 9.708.
-
Verify user portal is enabledIn the web admin interface, go to Authentication > User Portal > Settings to check if the User Portal service is enabled.Affected if The User Portal is enabled and the version is below 9.708.
-
Check for user portal accountsIn the web admin interface, go to Authentication > Users and look for user accounts that have access to the User Portal.Affected if User portal accounts exist and the version is below 9.708, meaning an authenticated attacker could exploit the SQL injection.
Your environment is affected if the Sophos SG UTM Up2date version is below 9.708 MR8 and the user portal is enabled with active accounts.
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 · scoped9.708
Upgrade SG UTM to version 9.708 MR8 or later to patch the SQL injection vulnerability.
9.708 MR8 or later
- Upgrade Sophos SG UTM to version 9.708 MR8 or later to remediate the SQL injection vulnerability
- Verify the upgrade was successful by checking the Up2date version in the UTM management interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36807 — 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-2021-36807 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