dbcve.org
InjectionWeakness · CWE-74

CVE-2024-11305

MEDIUM · 6.3 CVSS v3.1 Published 2024-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A vulnerability classified as critical was found in Altenergy Power Control Software up to 20241108. This vulnerability affects the function get_status_zigbee of the file /index.php/display/status_zigbee. The manipulation of the argument date leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 Altenergy Power Control Software's get_status_zigbee function at /index.php/display/status_zigbee. The 'date' parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries.

MitigationImplement parameterized queries or prepared statements for the date parameter; apply input validation and consider deploying a WAF as a compensating control until the vendor releases an official patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Confirm Altenergy Power Control Software is installed
    Check for the presence of the application by looking for web server directories containing 'altenergy', 'power control', or the specific file path /index.php in the web root. Inspect web server logs or configuration files to identify this application.
    Affected if The software is present on the system and serving web content.
  2. Identify the installed version of Altenergy Power Control Software
    Locate version information in configuration files, about pages, or the main index.php header comments. Check the application directory for version.txt, VERSION file, or examine the main PHP files for version constants.
    Affected if The installed version is unknown or falls within the vulnerable range (if version data is available).
  3. Verify the vulnerable endpoint exists
    Check if the path /index.php/display/status_zigbee is accessible by attempting to access it via HTTP/HTTPS or reviewing the application's URL routing configuration.
    Affected if The endpoint /index.php/display/status_zigbee exists and responds to requests.
  4. Confirm the date parameter is accepted
    Send a GET request to /index.php/display/status_zigbee with a test value for the date parameter, such as ?date=2024-01-01, and observe if the application processes it.
    Affected if The application accepts and processes the date parameter without rejecting it.
  5. Test for SQL injection vulnerability
    Submit a SQL injection payload in the date parameter (e.g., date=2024-01-01' OR '1'='1) and examine the response for SQL errors, unexpected behavior, or differences in output that indicate the input is not being sanitized as SQL-safe.
    Affected if The application exhibits SQL errors, data leakage, or altered behavior indicating unsanitized SQL input is being executed.

A user is affected if Altenergy Power Control Software is installed, the /index.php/display/status_zigbee endpoint is accessible, and the date parameter accepts unsanitized SQL input that produces SQL errors or unexpected query results.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for the date parameter; apply input validation and consider deploying a WAF as a compensating control until the vendor releases an official patch.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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