dbcve.org
Waybox Pro FirmwareOperating system · Enelx

CVE-2023-29120

HIGH · 8.8 CVSS v3.1 Published 2024-11-05
Fix available
A fix is available. Upgrade to 2.1.1.0_jb3vu096a or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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
Waybox Enel X web management application could be used to execute arbitrary OS commands and provide administrator’s privileges over the Waybox system.

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 confidence

Command injection vulnerability in Waybox Enel X web management application allows authenticated attackers to execute arbitrary operating system commands and escalate privileges to administrator level on the Waybox system.

MitigationApply vendor patch if available; otherwise restrict network access to the management interface and enforce strict authentication to limit exposure to trusted users only.

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
Waybox Pro FirmwareOperating system
Affected:< 2.1.1.0_jb3vu096a

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

CVSS:3.1/AV:A/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Locate the physical device or check system inventory for Waybox Enel X or Enelx Waybox Pro charging stations or energy management devices
    Affected if The device is a Waybox Enel X product and the firmware version is below 2.1.1.0_jb3vu096a
  2. Determine the installed firmware version
    Access the device admin interface or check system information panels for the firmware build number, typically found under Settings, System Info, or About sections
    Affected if The firmware version string is lower than 2.1.1.0_jb3vu096a or the version cannot be determined but the device is a Waybox Enel X unit
  3. Verify web management interface status
    Check if the web-based administration interface is enabled and accessible on the network, typically on ports 80 or 443
    Affected if The web management interface is exposed and the firmware version is below 2.1.1.0_jb3vu096a
  4. Review admin user accounts
    Examine the list of configured administrator accounts in the web management interface under User Management or Admin Settings
    Affected if Unexpected or unauthorized administrator accounts exist in the system
  5. Audit for command injection indicators
    Review web server logs, system logs, or any available audit trails for suspicious command patterns, unusual shell executions, or unexpected system calls originating from the web application
    Affected if Logs show anomalous commands or shell invocations that were not initiated by authorized administrators

You are affected if you have a Waybox Enel X device running firmware version lower than 2.1.1.0_jb3vu096a with the web management interface enabled.

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 2.1.1.0_jb3vu096a or later
Fixed in 2.1.1.0_jb3vu096a
Interim mitigation

Apply vendor patch if available; otherwise restrict network access to the management interface and enforce strict authentication to limit exposure to trusted users only.

Recommended fix Moderate confidence

2.1.1.0_jb3vu096a

  1. 1. Identify the current firmware version of the Waybox Pro device through the web management interface or device documentation
  2. 2. Navigate to the official Enel X Waybox support page or firmware download section at support-emobility.enelx.com
  3. 3. Download the firmware version 2.1.1.0_jb3vu096a or later
  4. 4. Access the Waybox Pro web management application as administrator
  5. 5. Locate the firmware update or system settings section in the management interface
  6. 6. Upload and apply the firmware version 2.1.1.0_jb3vu096a
  7. 7. Verify the upgrade was successful by checking the firmware version after reboot

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

Fix this in Waybox Pro Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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