CVE-2023-46807
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 web component of EPMM 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 the web component of EPMM prior to version 12.1.0.0 allows an authenticated user with appropriate privileges to execute arbitrary SQL queries, potentially enabling unauthorized access to or modification of sensitive data in 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 EPMM installation versionLocate the installed Ivanti Endpoint Manager Mobile version through the system administration console, registry, or installed packages listingAffected if the installed version is lower than 12.1.0.0
-
Verify web component is presentConfirm the EPMM web component (admin console or user-facing web interface) is installed and runningAffected if the web component exists and the version is below 12.1.0.0
-
Confirm authentication is configuredCheck whether user authentication is enabled for the EPMM web interfaceAffected if authentication is active and the EPMM version is below 12.1.0.0
-
Check for suspicious SQL-oriented web requestsReview web access logs for unusual SQL syntax or database commands in URL parameters or form inputs targeting the EPMM web componentAffected if anomalous SQL-like patterns appear in web logs and the version is below 12.1.0.0
If EPMM is installed with a version lower than 12.1.0.0 and the web component with authentication is enabled, the environment is affected by this SQL injection vulnerability.
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 vendor patch; alternatively, implement parameterized queries or input validation controls in the affected web component to mitigate SQL injection risks.
12.1.0.0
- 1. Backup the current EPMM installation and database before starting the upgrade process
- 2. Review the official Ivanti Endpoint Manager Mobile upgrade documentation for version 12.1.0.0
- 3. Download EPMM version 12.1.0.0 or later from the Ivanti portal or authorized distribution channel
- 4. Execute the upgrade following Ivanti's documented upgrade procedure for your specific deployment type
- 5. Verify the upgrade completed successfully by checking the EPMM admin console
- 6. Confirm the version displayed is 12.1.0.0 or later
- 7. Validate that the SQL injection vulnerability is remediated by testing the affected web component functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46807 — 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-46807 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