dbcve.org
Waybox Pro FirmwareOperating system · Enelx

CVE-2023-29126

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
The Waybox Enel X web management application contains a PHP-type juggling vulnerability that may allow a brute force process and under certain conditions bypass authentication.

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 has a PHP type juggling vulnerability that allows attackers to exploit loose type comparisons in authentication logic. This weakness enables brute force attacks and can potentially bypass authentication mechanisms under certain conditions.

MitigationApply available patches or updates from the vendor for the Waybox Enel X application. If no patch exists, implement additional authentication controls such as rate limiting, multi-factor authentication, or Web Application Firewall rules to mitigate brute force attempts.

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 Waybox firmware version
    Access the device administrative interface or check system information page to determine the currently installed firmware version. This is typically found in Settings > System > About or similar administrative location.
    Affected if The installed firmware version is lower than 2.1.1.0_jb3vu096a (e.g., 2.1.0.x, 2.0.x, or earlier releases).
  2. Confirm the web management application is accessible
    Verify that the Waybox web management interface (HTTP/HTTPS on the device LAN IP) is exposed and reachable from the network where verification is being performed.
    Affected if The web management interface is accessible and the firmware version is below 2.1.1.0_jb3vu096a.
  3. Locate authentication-related PHP files
    If file system access is available, examine PHP files in the web application directories, particularly those handling login, session validation, and user authentication functions. Look for code using loose comparison operators (==) in conditional statements related to authentication.
    Affected if PHP authentication code uses loose comparison (==) instead of strict comparison (===) and the firmware version is below 2.1.1.0_jb3vu096a.
  4. Inspect session validation logic
    Review PHP session handling code for type comparison in password verification or session token validation routines. Check for patterns where user-supplied values are compared using == rather than ===.
    Affected if Session validation or password comparison logic uses loose type comparison and the firmware is vulnerable.

The environment is affected if the Waybox Pro firmware version is below 2.1.1.0_jb3vu096a and the web management interface is accessible, allowing the PHP type juggling vulnerability in authentication logic to be exploited.

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 available patches or updates from the vendor for the Waybox Enel X application. If no patch exists, implement additional authentication controls such as rate limiting, multi-factor authentication, or Web Application Firewall rules to mitigate brute force attempts.

Recommended fix Moderate confidence

Waybox Pro Firmware version 2.1.1.0_jb3vu096a

  1. Obtain the firmware update 2.1.1.0_jb3vu096a from the vendor support portal at support-emobility.enelx.com
  2. Review the vendor's firmware upgrade instructions for Waybox Pro
  3. Apply the firmware update to the Waybox Pro device following the documented procedure
  4. Verify the firmware version has been successfully updated to 2.1.1.0_jb3vu096a or later
  5. Confirm the PHP type juggling vulnerability is no longer present by testing authentication flows

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-29126 — 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-29126 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