CVE-2023-29119
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 · uneditedWaybox Enel X web management application could execute arbitrary requests on the internal database via /admin/dbstore.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 confidenceThe Waybox Enel X web management application contains a critical injection vulnerability in /admin/dbstore.php that allows unauthenticated attackers to execute arbitrary requests on the internal database, likely through unsanitized user input being passed to database queries.
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< 2.1.1.0_jb3vu096aCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed firmware versionAccess the device's web management interface and navigate to the About, Status, or System Information page to locate the firmware version. Alternatively, check via command line if SSH/Telnet access is available using commands like 'cat /etc/version' or 'cat /etc/os-release'.Affected if The firmware version is lower than 2.1.1.0_jb3vu096a
-
Verify /admin/dbstore.php endpoint is exposedSend an HTTP request to the /admin/dbstore.php endpoint from an external location using a tool like curl: curl -v http://<device-ip>/admin/dbstore.phpAffected if The endpoint returns a valid HTTP response (200 OK) instead of a 403 Forbidden, 404 Not Found, or connection refused error, indicating the endpoint is network-accessible
-
Test for injection susceptibilitySend a request to /admin/dbstore.php with a test parameter containing a single quote or typical SQL injection payload (e.g., ?param=') and observe whether the response contains database error messages, SQL syntax warnings, or abnormal application behavior.Affected if The response includes database error messages, SQL syntax errors, or reveals information about the database structure
A device is affected if it runs Enelx Waybox Pro Firmware below version 2.1.1.0_jb3vu096a AND has the /admin/dbstore.php endpoint network-accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.1.1.0_jb3vu096a
Restrict network access to the /admin/ endpoint and apply vendor-provided patches. If no patch exists, implement strict input validation and parameterized queries in dbstore.php to prevent injection attacks.
2.1.1.0_jb3vu096a
- Obtain the Waybox Pro Firmware version 2.1.1.0_jb3vu096a from the official Enel X support source (support-emobility.enelx.com)
- Access the Waybox Enel X web management interface
- Navigate to the firmware update or system settings section
- Upload and apply firmware version 2.1.1.0_jb3vu096a
- Verify the firmware was successfully applied and the device is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-29119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29119 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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