CVE-2026-35555
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 · uneditedPowerSYSTEM Center feature for device project groups allows an authenticated user with limited permissions to perform an unauthorized deletion of project groups.
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 confidencePowerSYSTEM Center has a broken access control vulnerability in its device project groups feature. An authenticated user with limited or standard permissions can delete project groups they should not have authorization to delete, indicating missing or insufficient authorization checks on the deletion operation.
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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 PowerSYSTEM Center versionLocate the installed PowerSYSTEM Center version through the product's about dialog, help menu, or system information page typically accessible via the web interface or client applicationAffected if The installed version falls within the affected version range and the device project groups feature is in use
-
Confirm device project groups feature existenceNavigate to the device management or project organization section of the PowerSYSTEM Center interface and verify if project groups functionality is present and accessibleAffected if Project groups feature is enabled and available in the environment
-
Review user role assignmentsAccess the user management or role-based access control configuration panel to identify users assigned limited or standard permission rolesAffected if Users with limited or standard permissions exist in the system who have any access to project group management
-
Inspect project group deletion authorization controlsExamine the access control configuration, permissions matrix, or security settings related to project group operations. Check if role-based permissions explicitly control delete operations on project groupsAffected if No explicit authorization check or insufficient permission validation is configured for project group deletion, or the delete permission is granted to limited/standard roles
-
Test or verify deletion authorization for restricted usersUsing an account with limited or standard permissions, attempt to access and delete a project group that was created by a different user or belongs to a higher-privilege role. Observe if the deletion is allowed without proper authorizationAffected if A limited or standard permission user can successfully delete project groups they did not create or should not have authorization to delete
Your environment is affected if the installed PowerSYSTEM Center version is within the affected range and limited or standard permission users can delete project groups they should not have authorization to access.
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 proper role-based access control (RBAC) checks before executing project group deletions to verify the authenticated user has sufficient permissions for the specific resource being deleted.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35555 — 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-35555 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