CVE-2026-7694
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 · uneditedA flaw has been found in Acrel Electrical ECEMS Enterprise Microgrid Energy Efficiency Management System 1.3.0. The impacted element is an unknown function of the file /SubstationWEBV2/main/elecMaxMinAvgValue. Executing a manipulation of the argument fCircuitids can lead to sql injection. The attack can be launched remotely. The exploit has been published 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 confidenceSQL injection vulnerability in Acrel Electrical ECEMS Enterprise Microgrid Energy Efficiency Management System 1.3.0. The elecMaxMinAvgValue function in /SubstationWEBV2/main/elecMaxMinAvgValue endpoint fails to properly sanitize the fCircuitids parameter, allowing remote attackers to inject arbitrary SQL commands into the database query.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ECEMS web interface is accessibleAccess the application's main URL and verify the /SubstationWEBV2/ path responds. Look for the Acrel ECEMS login page or application interface.Affected if The application is reachable and appears to be Acrel ECEMS Enterprise Microgrid Energy Efficiency Management System.
-
Identify the installed ECEMS versionCheck the application for a version identifier. Common locations: login page footer, About page, help menu, or check HTTP response headers from /SubstationWEBV2/ requests. Compare the found version to 1.3.0.Affected if The installed version is exactly 1.3.0.
-
Verify the vulnerable endpoint existsSend an HTTP GET or POST request to /SubstationWEBV2/main/elecMaxMinAvgValue. A 200 response or application error indicates the endpoint exists and is reachable.Affected if The /SubstationWEBV2/main/elecMaxMinAvgValue endpoint is accessible without authentication or with valid credentials.
-
Confirm the fCircuitids parameter is acceptedSubmit a test request to the endpoint including the fCircuitids parameter (e.g., ?fCircuitids=1). Observe if the application processes the parameter without immediate rejection.Affected if The application accepts and processes the fCircuitids parameter without sanitization errors.
A user is affected if the Acrel ECEMS version is 1.3.0 and the /SubstationWEBV2/main/elecMaxMinAvgValue endpoint with the fCircuitids parameter is exposed and functional.
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.
From vendor dataImplement parameterized queries or prepared statements for all database interactions involving the fCircuitids parameter. Alternatively, deploy a WAF with SQL injection rules as an interim control until a vendor patch is available.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7694 — 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-2026-7694 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