dbcve.org
PanelApplication · Elizsoftware

CVE-2024-5958

HIGH · 8.8 CVSS v3.1 Published 2024-09-18
Fix available
A fix is available. Upgrade to 2.3.24 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Eliz Software Panel allows Command Line Execution through SQL Injection. This issue affects Panel: before v2.3.24.

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 · high confidence

SQL injection vulnerability in Eliz Software Panel versions before v2.3.24 allows authenticated attackers to execute arbitrary operating system commands via specially crafted SQL queries. This represents a critical escalation from standard SQL injection, as attackers can leverage database features to achieve command execution on the host system rather than merely exfiltrating or manipulating data.

MitigationUpgrade Eliz Software Panel to version v2.3.24 or later. Additionally, implement parameterized queries or prepared statements throughout the application to prevent SQL injection, and restrict database user privileges to minimize the impact of any future injection vulnerabilities.

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
PanelApplication
Affected:< 2.3.24

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate the installed version of Eliz Software Panel
    Check the application's version file, typically found in the installation directory (look for version.php, version.json, or similar metadata files). Alternatively, access the admin login interface and check any 'About' or 'System Information' pages that display the software version.
    Affected if The displayed version is below v2.3.24 (e.g., 2.3.23, 2.3.0, 1.x.x, etc.)
  2. Compare your version against the affected range
    If you cannot locate the version through the interface, check the application's header files, changelog, or the database configuration files that may contain version metadata. Cross-reference with the vendor's release notes for v2.3.24.
    Affected if Your version is any release prior to v2.3.24
  3. Confirm authentication is enabled for the application
    Verify that the Eliz Software Panel login functionality is active. Check whether user accounts can be created and whether the admin dashboard requires valid credentials to access.
    Affected if Authentication is enabled and user accounts exist in the system (the vulnerability requires an authenticated attacker)
  4. Identify SQL query entry points in the application
    Review application logs or use a web proxy to observe SQL queries being executed. Focus on endpoints that accept user input and pass it to database queries, particularly in admin or privileged areas.
    Affected if The application processes user-supplied input through direct SQL queries without visible parameterized query usage

You are affected if Eliz Software Panel is installed at any version prior to v2.3.24 and the application is accessible with active user authentication.

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.3.24 or later
Fixed in 2.3.24
Interim mitigation

Upgrade Eliz Software Panel to version v2.3.24 or later. Additionally, implement parameterized queries or prepared statements throughout the application to prevent SQL injection, and restrict database user privileges to minimize the impact of any future injection vulnerabilities.

Recommended fix High confidence

Panel v2.3.24

  1. 1. Back up the current Eliz Software Panel database and configuration files before attempting any upgrade.
  2. 2. Download the Eliz Software Panel version 2.3.24 or later from the official vendor source.
  3. 3. Review the upgrade documentation provided with the new version for any specific migration steps.
  4. 4. Apply the upgrade to the Panel following the vendor's recommended installation procedure.
  5. 5. After upgrading, verify the SQL injection vulnerability is remediated by testing input validation in affected areas.
  6. 6. Confirm all administrative credentials are still valid and access controls function correctly.
  7. 7. Monitor system logs for any anomalies following the upgrade.
Caveat Review release notes for v2.3.24 to check for any configuration or feature changes that may affect existing setup

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

Fix this in Panel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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