CVE-2023-29126 is a medium severity flaw (CVSS 4.2) in the web management software of the Enel X Waybox Pro 3.0 EV charger. A PHP type juggling weakness may let a brute force attempt bypass authentication under certain conditions. The vendor fixed it in firmware 2.1.1.0_JB3VU096A, delivered as a remote update to connected chargers.
What's affected
The bulletin lists the Enel X Waybox Pro 3.0 charger running firmware before 2.1.1.0_JB3VU096A. Its introduction refers to the Waybox Pro and Plus 3.0 chargers, while the affected products section names only the Pro, so owners of the Plus should confirm with the vendor.
The NVD record lists the Waybox Pro firmware and the Waybox Pro 3.0 hardware. Fixed version: 2.1.1.0_JB3VU096A, which the vendor says it delivered as a remote firmware update.
How to check if you're exposed
There is no package to query here. Work from the charger itself and the vendor.
- List every Waybox Pro or Plus 3.0 unit you own or manage, with its location and network placement.
- Record the firmware version for each. If you cannot read it directly, ask Enel X Way support or use the Enel X Way mobile app, which the bulletin names as the route for units that are not online.
- Treat any unit on a firmware version earlier than 2.1.1.0_JB3VU096A as exposed until it is updated.
This is a device or appliance issue, not a package you pull from a registry, so a dependency scan will not see it. Safeguard's free in-browser scan at https://gold.safeguard.sh/scan reads dependency manifests and will not detect firmware running on hardware. Use your asset inventory instead.
What to do now
- Confirm each charger is on firmware 2.1.1.0_JB3VU096A or later.
- If a charger is not connected to the internet, follow the vendor's instructions in the Enel X Way mobile app to apply the update.
- Until you have confirmed the update, keep the charger's management interface off untrusted networks and limit who can reach it.
- Record the update in your asset register so the next audit can see the fixed version.
Why it matters
The vendor calls this an insecure loose comparison. In PHP, a loose comparison can treat values of different types as equal, so a check that looks strict can pass for input it should reject. The record says this may allow a brute force process and, under certain conditions, bypass authentication.
The score is only 4.2 because the attack needs specific conditions and a high effort process. It is still worth fixing in the same update. The standard code level defence is to use strict comparison and to compare hashes with a purpose built function.
The record classifies the weakness as CWE-1287. The bulletin states that these issues were found by PCAutomotive and confirmed by Enel X Way, that the vendor knows of no real attacks on any installed charger, and that no personal data would be accessible in an attack. Those are the vendor's statements, and this CVE is not on the CISA Known Exploited Vulnerabilities list.
Quick check
Why is this only Medium?
The record's score reflects the conditions needed and the brute force effort. The vendor fix is the same firmware as the other Waybox issues.
What is type juggling?
It is PHP's automatic conversion between types during a loose comparison, which can make unequal values compare as equal.
Sources
Last reviewed: 19 October 2026.