CVE-2021-27234
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 issue was discovered in Mutare Voice (EVM) 3.x before 3.3.8. The web application suffers from SQL injection on Adminlog.asp, Archivemsgs.asp, Deletelog.asp, Eventlog.asp, and Evmlog.asp.
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 confidenceSQL injection vulnerability in Mutare Voice (EVM) 3.x allows unauthenticated attackers to inject malicious SQL queries via multiple ASP pages (Adminlog.asp, Archivemsgs.asp, Deletelog.asp, Eventlog.asp, Evmlog.asp), potentially enabling data exfiltration or complete database compromise.
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>= 3.0.0, < 3.3.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Mutare Voice versionLocate the installation directory or check the product About/Version information within the application interface. Common locations include the program installation folder or the web application's footer/version page.Affected if The installed version is 3.0.0 through 3.3.7 (any version >= 3.0.0 and < 3.3.8)
-
Locate vulnerable ASP pagesCheck the web root directory for the presence of Adminlog.asp, Archivemsgs.asp, Deletelog.asp, Eventlog.asp, and Evmlog.asp. These are typically found in the /admin or /eva subdirectories of the web application.Affected if Any of these ASP pages exist in the web-accessible directory
-
Verify network exposureDetermine if these ASP endpoints are reachable from unauthenticated network locations. Attempt to access one of the vulnerable pages (e.g., http://[host]/[path]/Adminlog.asp) without providing credentials.Affected if The pages are accessible without authentication from external/untrusted networks
-
Review database logs for suspicious queriesExamine database transaction logs, SQL Server logs, or application audit logs for unusual or malicious SQL syntax within requests targeting the vulnerable ASP pages. Look for patterns like UNION SELECT, OR 1=1, or DROP TABLE.Affected if Unexpected SQL injection patterns appear in logs related to these ASP pages
A user is affected if Mutare Voice (EVM) version 3.0.0 through 3.3.7 is installed AND the vulnerable ASP pages (Adminlog.asp, Archivemsgs.asp, Deletelog.asp, Eventlog.asp, Evmlog.asp) are network-accessible without authentication.
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 · scoped3.3.8
Upgrade to Mutare Voice (EVM) version 3.3.8 or later to obtain the patched code. If immediate patching is not feasible, restrict network access to these administrative ASP endpoints and implement WAF rules as a compensating control.
3.3.8
- 1. Back up the current Mutare Voice installation and its database before proceeding with any upgrade.
- 2. Download Mutare Voice version 3.3.8 or later from the official vendor source (www.mutare.com).
- 3. Follow Mutare's documented upgrade procedure to install version 3.3.8, ensuring all configuration settings are preserved.
- 4. After installation, verify the upgrade was successful by checking the application version.
- 5. Test the previously affected pages (Adminlog.asp, Archivemsgs.asp, Deletelog.asp, Eventlog.asp, Evmlog.asp) to confirm the SQL injection vulnerability is remediated.
- 6. Monitor the application logs for any suspicious SQL-like activity to ensure no exploitation occurred prior to patching.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27234 — 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-27234 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