dbcve.org
Mx Se FirmwareOperating system · Zultys

CVE-2023-43743

HIGH · 8.8 CVSS v3.1 Published 2023-12-08
Fix available
A fix is available. Upgrade to 16.0.4 / 17.0.10 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A SQL injection vulnerability in Zultys MX-SE, MX-SE II, MX-E, MX-Virtual, MX250, and MX30 with firmware versions prior to 17.0.10 patch 17161 and 16.04 patch 16109 allows an authenticated attacker to execute arbitrary SQL queries on the backend database via the filter parameter in requests to the /newapi/ endpoint in the Zultys MX web interface.

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

A SQL injection vulnerability exists in Zultys MX series appliances (MX-SE, MX-SE II, MX-E, MX-Virtual, MX250, MX30) in the filter parameter of the /newapi/ endpoint. An authenticated attacker can inject arbitrary SQL commands via this parameter to read, modify, or delete data in the backend database.

MitigationApply vendor firmware updates 17.0.10 patch 17161 or 16.04 patch 16109. Until patched, restrict access to the /newapi/ endpoint using network ACLs or VPN access controls.

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
Mx Se FirmwareOperating system
Affected:< 16.0.4>= 17.0.6, < 17.0.10
Mx Se Ii FirmwareOperating system
Affected:< 16.0.4>= 17.0.6, < 17.0.10
Mx E FirmwareOperating system
Affected:< 16.0.4>= 17.0.6, < 17.0.10
Mx Virtual FirmwareOperating system
Affected:< 16.0.4>= 17.0.6, < 17.0.10
Mx250 FirmwareOperating system
Affected:< 16.0.4>= 17.0.6, < 17.0.10
Mx30 FirmwareOperating system
Affected:< 16.0.4>= 17.0.6, < 17.0.10

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Zultys MX appliance model
    Access the device administrative interface or check system documentation to confirm the model is one of: MX-SE, MX-SE II, MX-E, MX-Virtual, MX250, or MX30
    Affected if Model is not one of these listed MX series appliances (not vulnerable)
  2. Check firmware version
    In the device admin panel, navigate to System > Status or use the command line to run 'show version' or similar command to retrieve the installed firmware version
    Affected if Firmware version is below 16.0.4 OR is 17.0.6 through 17.0.9 (vulnerable)
  3. Verify /newapi/ endpoint accessibility
    Attempt to access https://[device-ip]/newapi/ from a network perspective to confirm the endpoint is reachable (this is the vulnerable endpoint)
    Affected if Endpoint is accessible from untrusted networks (exposed)
  4. Confirm authentication method
    Review whether user authentication is enabled and functional on the /newapi/ endpoint (the SQL injection requires authenticated access)
    Affected if Authentication is not required or is bypassed for this endpoint

The environment is affected if the device is a Zultys MX series appliance (MX-SE, MX-SE II, MX-E, MX-Virtual, MX250, or MX30) running firmware version below 16.0.4 or between 17.0.6 and 17.0.9, and the /newapi/ endpoint is accessible with authenticated access possible.

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 16.0.4 / 17.0.10 or later
Fixed in 16.0.417.0.10
Interim mitigation

Apply vendor firmware updates 17.0.10 patch 17161 or 16.04 patch 16109. Until patched, restrict access to the /newapi/ endpoint using network ACLs or VPN access controls.

Recommended fix High confidence

Upgrade to firmware 17.0.10 patch 17161 or 16.0.4 patch 16109

  1. Identify the current firmware version of the Zultys MX device through the admin web interface
  2. Download the fixed firmware version (17.0.10 patch 17161 or 16.0.4 patch 16109) from the official Zultys support portal
  3. Backup the current device configuration before proceeding with the update
  4. Access the device admin console and navigate to the firmware update section
  5. Upload and apply the appropriate fixed firmware version
  6. After the update completes, verify the new firmware version is installed (17.0.10 with patch 17161 or 16.0.4 with patch 16109)
  7. Confirm the /newapi/ endpoint no longer accepts malicious SQL injection payloads in the filter parameter
  8. Test that normal device functionality remains intact after the upgrade
Caveat Firmware upgrades typically require planned downtime; test in a non-production environment first

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

Fix this in Mx Se Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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