CVE-2026-9550
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 was determined in Acrel Electrical EEMS Enterprise Power Operation and Maintenance Cloud Platform 1.3.0. Affected by this issue is some unknown functionality of the file /SubstationWEBV2/app/..;/main/upfile. Executing a manipulation of the argument path can lead to path traversal. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. 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 confidencePath traversal vulnerability in the file upload functionality of Acrel Electrical EEMS Enterprise Power Operation and Maintenance Cloud Platform 1.3.0. The endpoint /SubstationWEBV2/app/..;/main/upfile does not properly validate the path argument, allowing attackers to use '..;/' directory traversal sequences to access or write files outside the intended directory. This is a remote exploitable file operation vulnerability with CVSS 7.3.
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.
-
Identify if Acrel EEMS platform is presentLocate the SubstationWEBV2 web application directory on the server or confirm the application is accessible via HTTP by accessing the /SubstationWEBV2 endpointAffected if The SubstationWEBV2 component of Acrel EEMS Enterprise Power Operation and Maintenance Cloud Platform is found on the system
-
Confirm the installed versionCheck the application version information, typically found in the application about page, metadata files within the web root, or by querying the application's version endpointAffected if The installed version matches 1.3.0 or falls within the affected version range
-
Verify the vulnerable endpoint existsSend an HTTP request to /SubstationWEBV2/app/..;/main/upfile and observe the responseAffected if The endpoint responds with any HTTP status code (including error codes), indicating the path is being processed by the application
-
Check if path traversal filter can be bypassedSend a test request using the '..;/' bypass pattern (e.g., /SubstationWEBV2/app/..;/main/upfile or similar path) and examine whether the filter is bypassedAffected if The '..;/' pattern bypasses the path traversal filter and allows access to paths outside the intended directory
A system is affected if it runs Acrel Electrical EEMS Enterprise Power Operation and Maintenance Cloud Platform version 1.3.0 with the SubstationWEBV2 component and the /SubstationWEBV2/app/..;/ endpoint accepts the path traversal bypass pattern.
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 strict input validation to reject directory traversal sequences ('..' or encoded variants) in file path parameters, and store all uploaded files outside web-accessible directories with appropriate access controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9550 — 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-9550 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