CVE-2021-36722
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 · uneditedEmuse - eServices / eNvoice SQL injection can be used in various ways ranging from bypassing login authentication or dumping the whole database to full RCE on the affected endpoints. The SQLi caused by CWE-209: Generation of Error Message Containig Sensetive Information, showing parts of the aspx code and the webroot location , information an attacker can leverage to further compromise the host.
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 confidenceA critical SQL injection vulnerability in Emuse eServices/eNvoice allows attackers to bypass authentication, dump database contents, or achieve remote code execution. The vulnerability stems from improper error handling (CWE-209) that exposes sensitive information including ASPX source code fragments and webroot paths in error messages, providing attackers with valuable reconnaissance data to further compromise the host.
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 dataall versionsCVSS 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.
-
Confirm Emuse eServices/Envoice is presentCheck your web server for Emuse eServices or Envoice application files, or probe your web application for known Emuse-related paths/endpoints in HTTP responsesAffected if The application is found running in your environment
-
Trigger an application errorSend a malformed request to the application (such as invalid input in parameters, or access to non-existent resources) to elicit an error responseAffected if The application returns error pages instead of generic HTTP 500 responses
-
Inspect error message contentExamine the full error response body for exposed sensitive information: look for fragments of ASPX code (look for <%@, <script runat, or C# code patterns), file path strings (such as C:\inetpub\ or /var/www/), or stack tracesAffected if Error messages contain ASPX source code fragments, full file system paths, or detailed stack traces that reveal internal application structure
You are affected if Emuse eServices or Envoice is running and returns detailed error messages that expose source code fragments or file system paths to attackers.
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.
From vendor dataImplement parameterized queries/prepared statements to eliminate SQL injection vectors, and replace detailed error messages with generic responses while logging sensitive details server-side for debugging only. Consider deploying a WAF as a compensating control during remediation.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36722 — 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-36722 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