CVE-2026-7695
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 vulnerability has been found in Acrel Electrical EEMS Enterprise Power Operation and Maintenance Cloud Platform 1.3.0. This affects an unknown function of the file /SubstationWEBV2/main/elecMaxMinAvgValue. The manipulation of the argument fCircuitids leads to sql injection. The attack may 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 · moderate confidenceSQL injection vulnerability in Acrel Electrical EEMS Enterprise Power Operation and Maintenance Cloud Platform v1.3.0. The fCircuitids parameter in the /SubstationWEBV2/main/elecMaxMinAvgValue endpoint is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. The exploit is publicly available and the vendor failed to respond to early disclosure.
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 Acrel EEMS installationLocate the web application installation directory or identify the server hosting Acrel Electrical EEMS Enterprise Power Operation and Maintenance Cloud Platform. Check version information in application metadata, about page, or configuration files.Affected if The installed version matches v1.3.0 or falls within an unknown range around this version.
-
Identify the vulnerable endpointCheck if the URL path /SubstationWEBV2/main/elecMaxMinAvgValue is accessible on the web server. This may require reviewing web server configuration files, reverse proxy settings, or performing a web path scan.Affected if The endpoint /SubstationWEBV2/main/elecMaxMinAvgValue is reachable and responds to requests.
-
Verify fCircuitids parameter exposureInspect HTTP requests to the elecMaxMinAvgValue endpoint. Determine whether the fCircuitids parameter is accepted via GET or POST request body.Affected if The fCircuitids parameter is accepted and processed by the application without being filtered or validated.
-
Review application logs for SQL injection attemptsExamine web server access logs and application logs for suspicious patterns in the fCircuitids parameter, such as SQL keywords (UNION, SELECT, OR, AND), quotes, or common SQL injection payloads.Affected if Logs contain SQL injection payloads or anomalous queries targeting the fCircuitids parameter.
The environment is affected if Acrel Electrical EEMS Enterprise Power Operation and Maintenance Cloud Platform v1.3.0 is running and the /SubstationWEBV2/main/elecMaxMinAvgValue endpoint with the fCircuitids parameter is exposed.
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 dataSince the vendor did not respond, implement input validation and parameterized queries on the fCircuitids parameter, or deploy a WAF rule to block SQL injection payloads. Consider network segmentation to limit exposure until a vendor patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7695 — 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-7695 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