dbcve.org
Waybox Pro FirmwareOperating system · Enelx

CVE-2023-29118

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 execute arbitrary requests on the internal database via /admin/versions.php.

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

The Waybox Enel X web management application contains a vulnerability in /admin/versions.php that allows execution of arbitrary database requests, likely due to unsanitized input leading to SQL injection.

MitigationApply vendor patches immediately. If no patch available, disable the /admin/versions.php endpoint or implement strict input validation and parameterized queries to prevent SQL injection.

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 installed firmware version
    Access the device administrative interface or check system information pages to determine the current firmware version. This is typically found in Settings, About, or System Status sections of the Waybox web management application.
    Affected if The installed firmware version is lower than 2.1.1.0_jb3vu096a (for example, 2.0.x, 1.x, or any version string that sorts lexicographically before 2.1.1.0_jb3vu096a).
  2. Locate the versions.php endpoint
    Verify whether the file /admin/versions.php exists on the web server. This can be attempted via direct HTTP request to the endpoint or by checking the web root directory structure if you have filesystem access.
    Affected if The /admin/versions.php file is present and accessible on the web server.
  3. Confirm admin interface is enabled
    Determine if the /admin/ administrative interface is enabled and reachable. This is typically accessible at the base URL of the Waybox management application followed by /admin/.
    Affected if The administrative interface at /admin/ is accessible without being explicitly disabled or restricted by network configuration.
  4. Check for unsanitized input handling
    Review the application's input handling behavior when accessing /admin/versions.php. The vulnerability stems from unsanitized parameters being passed to database queries. If you can examine the application logs or error outputs, look for SQL syntax errors or unexpected database behavior when non-standard input is provided.
    Affected if The application processes requests to /admin/versions.php without proper input validation or parameterized queries, allowing arbitrary database interaction.

You are affected if your Waybox Pro firmware version is below 2.1.1.0_jb3vu096a AND the /admin/versions.php endpoint is accessible and the admin interface is 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 patches immediately. If no patch available, disable the /admin/versions.php endpoint or implement strict input validation and parameterized queries to prevent SQL injection.

Recommended fix Moderate confidence

Waybox Pro Firmware version 2.1.1.0_jb3vu096a or later

  1. 1. Identify the current firmware version of the Waybox Pro device through the web management interface or device documentation
  2. 2. If the current version is less than 2.1.1.0_jb3vu096a, download the firmware update from the official Enel X Waybox support portal at support-emobility.enelx.com
  3. 3. Follow the manufacturer's official firmware update procedure, which typically involves accessing the admin panel and using a firmware upload or update function
  4. 4. After applying the update, verify the device is running version 2.1.1.0_jb3vu096a or later
  5. 5. Confirm the /admin/versions.php endpoint is no longer vulnerable by testing that SQL injection payloads are rejected

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

Fix this in Waybox Pro Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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