Web ApplianceApplication · Sophos

CVE-2020-36692

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-04
Fix available
A fix is available. Upgrade to 4.3.10.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A reflected XSS via POST vulnerability in report scheduler of Sophos Web Appliance versions older than 4.3.10.4 allows execution of JavaScript code in the victim browser via a malicious form that must be manually submitted by the victim while logged in to SWA.

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 confidence

A reflected XSS vulnerability exists in the report scheduler of Sophos Web Appliance versions prior to 4.3.10.4. Attackers can inject malicious JavaScript into a form that gets reflected back and executed in the victim's browser when the authenticated user manually submits the crafted form.

MitigationUpgrade Sophos Web Appliance to version 4.3.10.4 or later to patch the reflected XSS vulnerability in the report scheduler component.

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
Web ApplianceApplication
Affected:< 4.3.10.4

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
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 checks

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

  1. Confirm Sophos Web Appliance installation
    Check if Sophos Web Appliance is present on the system by looking for typical installation directories such as /opt/sophos-avi/ or /opt/sophos-alert/ or by running 'ls /opt/' to list Sophos-related directories.
    Affected if The product is not found on the system.
  2. Identify installed version
    Locate the version file or check the admin interface for the Sophos Web Appliance version. This is typically accessible via the web admin portal or by examining version files within the Sophos installation directory.
    Affected if The installed version cannot be determined or is not Sophos Web Appliance.
  3. Compare version to vulnerable range
    Compare your installed version number to the affected range: versions prior to 4.3.10.4. If the version starts with 4.3.10.x, verify the specific patch level (4.3.10.4 and later are fixed).
    Affected if The installed version is 4.3.10.3 or earlier, or any version starting with 4.3.9, 4.3.8, or lower.
  4. Verify report scheduler access
    Log into the Sophos Web Appliance admin interface and navigate to the report scheduler functionality. This feature is typically found under Reporting or Scheduler sections of the web admin panel.
    Affected if The report scheduler module is accessible and the user can create or submit scheduled reports.

You are affected if Sophos Web Appliance is installed with a version lower than 4.3.10.4 and the report scheduler module is accessible in your environment.

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 4.3.10.4 or later
Fixed in 4.3.10.4
Interim mitigation

Upgrade Sophos Web Appliance to version 4.3.10.4 or later to patch the reflected XSS vulnerability in the report scheduler component.

Recommended fix High confidence

4.3.10.4

  1. Log in to the Sophos Web Appliance administrative console
  2. Navigate to the system maintenance or upgrade section
  3. Locate the firmware/software update option
  4. Check current version is below 4.3.10.4
  5. Apply the update to version 4.3.10.4 or later
  6. Verify the upgrade was successful by confirming the new version number

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

Fix this in Web Appliance Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-36692 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-36692 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