dbcve.org
VoiceApplication · Mutare

CVE-2021-27236

CRITICAL · 9.8 CVSS v3.1 Published 2021-02-16
Fix available
A fix is available. Upgrade to 3.3.8 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 issue was discovered in Mutare Voice (EVM) 3.x before 3.3.8. getfile.asp allows Unauthenticated Local File Inclusion, which can be leveraged to achieve Remote Code Execution.

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

Mutare Voice (EVM) versions before 3.3.8 contain an unauthenticated Local File Inclusion (LFI) vulnerability in getfile.asp. Attackers can exploit this to read sensitive local files, and the vulnerability can be chained to achieve Remote Code Execution.

MitigationUpgrade to Mutare Voice version 3.3.8 or later. If immediate patching is not possible, implement web application firewall rules to block directory traversal patterns in the getfile.asp endpoint.

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
VoiceApplication
Affected:>= 3.0.0, < 3.3.8

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. Locate Mutare Voice installation
    Search the system for Mutare Voice installation directories or check the web server root for Mutare Voice/EVM related folders. Common locations include C:\Program Files\Mutare\Voice or IIS web roots.
    Affected if The application is installed on the system.
  2. Identify installed version
    Check version files, registry entries, or the application itself for version information. Compare the found version against the affected range: 3.0.0 to 3.3.7 (versions before 3.3.8 are affected).
    Affected if The installed version is 3.0.0 or higher but lower than 3.3.8.
  3. Verify getfile.asp exists
    Locate the getfile.asp file within the Mutare Voice web directory. This is the vulnerable endpoint for the LFI flaw.
    Affected if The getfile.asp file exists in the Mutare Voice web application directory.
  4. Confirm endpoint accessibility
    Verify the getfile.asp endpoint is accessible without authentication. Since this is an unauthenticated LFI, the endpoint should respond to requests without requiring login credentials.
    Affected if The getfile.asp endpoint is reachable without authentication.

You are affected if Mutare Voice version is 3.0.0 or higher but lower than 3.3.8 AND the getfile.asp endpoint exists and is accessible without authentication.

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

Upgrade to Mutare Voice version 3.3.8 or later. If immediate patching is not possible, implement web application firewall rules to block directory traversal patterns in the getfile.asp endpoint.

Recommended fix High confidence

3.3.8

  1. 1. Create a complete backup of the current Mutare Voice installation including configuration files and databases.
  2. 2. Download Mutare Voice version 3.3.8 from the official Mutare website (www.mutare.com) or official distribution channels.
  3. 3. Review the official Mutare Voice upgrade documentation for version 3.3.8.
  4. 4. Execute the upgrade process according to Mutare's documented upgrade procedure.
  5. 5. After upgrade, verify the getfile.asp endpoint is no longer vulnerable to unauthenticated LFI.
  6. 6. Confirm the installed version is 3.3.8 or higher.
  7. 7. Test that normal Voice functionality is operational after the upgrade.

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

Fix this in Voice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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