CVE-2023-46806
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 SQL Injection vulnerability in a web component of EPMM versions before 12.1.0.0 allows an authenticated user with appropriate privilege to access or modify data in the underlying database.
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 confidenceSQL injection vulnerability in a web component of EPMM versions before 12.1.0.0 allows authenticated users with appropriate privileges to execute arbitrary SQL queries, potentially allowing unauthorized access to or modification of the underlying database.
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< 12.1.0.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
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 the installed EPMM versionAccess the EPMM administration console or use the product's built-in version check mechanism (typically available in About or System Information sections of the web interface)Affected if The displayed version number is less than 12.1.0.0 (for example, 11.x.x.x or earlier)
-
Confirm the web component is accessibleAttempt to reach the EPMM web portal URL (typically on port 443 or 8443) from an authorized networkAffected if The web interface loads and accepts authentication requests, indicating the vulnerable web component is active
-
Verify authentication is enabledCheck if user accounts with privileges to access the web component exist in the EPMM user management sectionAffected if At least one user account with appropriate privileges is active, as the vulnerability requires authenticated access
Your environment is affected if the installed EPMM version is below 12.1.0.0 and the web component with authentication is accessible to authorized users.
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 · scoped12.1.0.0
Upgrade to EPMM version 12.1.0.0 or later to obtain the security patch, or apply vendor-supplied patches if available.
12.1.0.0
- 1. Identify the current EPMM version by accessing the admin console or checking system information
- 2. Create a full backup of the EPMM database and configuration settings before proceeding with any upgrade
- 3. Review Ivanti Endpoint Manager Mobile upgrade documentation for your current version to ensure compatibility
- 4. Download the EPMM 12.1.0.0 installation package from the official Ivanti download portal
- 5. Schedule a maintenance window and perform the upgrade following Ivanti's documented upgrade procedure
- 6. After upgrade completion, verify the EPMM services are running correctly
- 7. Log into the admin console and confirm version displays as 12.1.0.0 or higher
- 8. Test critical functionality to ensure normal operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46806 — 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-2023-46806 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