dbcve.org
MetadefenderApplication · Opswat

CVE-2018-16275

HIGH · 7.8 CVSS v3.0 Published 2018-08-31
Fix available
A fix is available. Upgrade to 4.11.2 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
OPSWAT MetaDefender before v4.11.2 allows CSV injection.

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

OPSWAT MetaDefender before v4.11.2 is vulnerable to CSV injection, where maliciously crafted input can be embedded into CSV export functionality. When users open the exported CSV file in spreadsheet applications, embedded formula characters (such as =, +, -, @) can trigger arbitrary command execution or data exfiltration.

MitigationUpgrade to MetaDefender v4.11.2 or later. Until patched, exercise caution when opening CSV exports from the application and consider disabling formula interpretation in spreadsheet software.

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.11.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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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. Identify MetaDefender version
    Log into the MetaDefender web interface and navigate to the About or Settings section to view the installed version. Alternatively, check the installation directory or package manager for the installed MetaDefender version number.
    Affected if The displayed version is below 4.11.2 (for example, 4.11.1, 4.10.x, or earlier)
  2. Confirm version via API or command line
    Use the MetaDefender API endpoint /api/version or the command-line interface tool provided with MetaDefender to retrieve the exact version number.
    Affected if The API or CLI returns a version string lower than 4.11.2
  3. Locate CSV export functionality
    In the MetaDefender web interface, browse to sections that support file scanning results or reporting, such as Scan History, Quarantine, or Reports, and identify if a CSV export or download option exists.
    Affected if CSV export feature is present and the MetaDefender version is below 4.11.2

If the installed MetaDefender version is below 4.11.2 and the CSV export feature is accessible, the environment is vulnerable to CVE-2018-16275.

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.

From vendor data
Upgrade available Upgrade to 4.11.2 or later
Fixed in 4.11.2
Interim mitigation

Upgrade to MetaDefender v4.11.2 or later. Until patched, exercise caution when opening CSV exports from the application and consider disabling formula interpretation in spreadsheet software.

Fix this in Metadefender Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,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 $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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