dbcve.org
MetadefenderApplication · Opswat

CVE-2022-40778

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-19
Fix available
A fix is available. Upgrade to 4.13.0 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 stored Cross-Site Scripting (XSS) vulnerability in OPSWAT MetaDefender ICAP Server before 4.13.0 allows attackers to execute arbitrary JavaScript or HTML because of the blocked page response.

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

Stored Cross-Site Scripting (XSS) vulnerability in OPSWAT MetaDefender ICAP Server prior to version 4.13.0. The vulnerability exists in the blocked page response mechanism, allowing attackers to inject malicious JavaScript or HTML that gets stored and executed when users view blocked content pages.

MitigationUpgrade to MetaDefender ICAP Server version 4.13.0 or later to obtain the patch for this vulnerability.

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
MetadefenderApplication
Affected:< 4.13.0

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 MetaDefender ICAP Server is installed
    Check for the presence of MetaDefender ICAP Server in your system services or installed applications list
    Affected if The software is not found in your environment, you are not affected
  2. Identify the installed version
    Run the command or check the admin interface to retrieve the MetaDefender ICAP Server version number (typically available in the About section of the admin panel or via command line with product-specific flags)
    Affected if The version cannot be determined, manual verification is required
  3. Compare version against affected range
    Compare your installed version to the affected range: any version prior to 4.13.0 is vulnerable
    Affected if Your installed version is 4.13.0 or later, you are NOT affected; if it is any version below 4.13.0, you ARE affected
  4. Verify ICAP blocking is enabled
    Check the MetaDefender ICAP Server configuration to confirm content blocking is active and the blocked page response feature is in use
    Affected if The blocking functionality is disabled and not in use, exploitation is not possible in practice even on vulnerable versions

You are affected if MetaDefender ICAP Server is running with a version lower than 4.13.0 and content blocking is enabled, allowing the stored XSS in the blocked page response to be triggered.

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.13.0 or later
Fixed in 4.13.0
Interim mitigation

Upgrade to MetaDefender ICAP Server version 4.13.0 or later to obtain the patch for this vulnerability.

Recommended fix Moderate confidence

MetaDefender ICAP Server 4.13.0 or later

  1. 1. Back up the current MetaDefender ICAP Server configuration and data before proceeding with the upgrade.
  2. 2. Download MetaDefender ICAP Server version 4.13.0 or later from the official OPSWAT portal or download center.
  3. 3. Stop the MetaDefender ICAP Server service to ensure no active connections during the upgrade.
  4. 4. Install or apply the upgrade following the standard OPSWAT installation documentation for your platform.
  5. 5. Verify that the service starts successfully after the upgrade.
  6. 6. Test that the previously vulnerable functionality (blocked page responses) no longer executes injected JavaScript/HTML code.
  7. 7. Verify that the MetaDefender ICAP Server is functioning normally with all expected features.

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

Fix this in Metadefender Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40778 — 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-2022-40778 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