dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-33570

MEDIUM · 5.7 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
PowerSYSTEM Center REST API endpoint for devices allows a low privilege authenticated user to access information normally limited by operational permissions.

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 confidence

PowerSYSTEM Center REST API endpoint for devices contains an authorization bypass where a low-privilege authenticated user can access information restricted by operational permissions. The API fails to properly enforce permission checks, allowing users to retrieve device data they should not have access to based on their assigned role.

MitigationImplement proper role-based access control (RBAC) checks on the device API endpoint to verify user permissions before returning sensitive information. Validate that the authenticated user's operational permissions match the requested device data.

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
High
Integrity
None
Availability
None

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

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 PowerSYSTEM Center installation and version
    Locate the PowerSYSTEM Center installation directory and check the version file or executable properties. Common locations include /opt/powersystemcenter/ or C:\Program Files\PowerSYSTEM Center\. Look for a version.txt, about dialog, or use the product's built-in version command if available.
    Affected if The installed version matches any affected version of PowerSYSTEM Center (no specific version range provided; compare your version to the vendor's advisory).
  2. Verify REST API service is enabled
    Check the PowerSYSTEM Center configuration files or service management console to determine if the REST API endpoint for devices is enabled and accessible. Look for configuration files such as rest-api-config.xml, server.xml, or similar in the config directory.
    Affected if The REST API service for devices is running and exposed (the vulnerability applies to the API endpoint).
  3. Review user role and permission assignments
    Access the PowerSYSTEM Center administrative console or user management configuration. Examine the operational permissions assigned to user roles, specifically focusing on which roles have restricted access to device data.
    Affected if Low-privilege user accounts exist with operational permissions that should restrict access to certain device information.
  4. Inspect API authorization configuration
    Examine the REST API authorization configuration files (such as web.xml, spring-security.xml, or similar) in the PowerSYSTEM Center config directory. Look for the device endpoint access control rules and verify if permission validation is properly enforced.
    Affected if The API endpoint lacks proper RBAC enforcement or the permission check logic is missing or bypassed for device data requests.
  5. Check audit logs for unauthorized access patterns
    Review PowerSYSTEM Center audit logs for instances where low-privilege users successfully retrieved device data they should not have access to based on their role permissions.
    Affected if Audit logs show low-privilege users accessing device information outside their assigned operational permissions.

A user is affected if PowerSYSTEM Center with the REST API for devices is running and low-privilege authenticated users can retrieve device data that should be restricted by their assigned role permissions.

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 proper role-based access control (RBAC) checks on the device API endpoint to verify user permissions before returning sensitive information. Validate that the authenticated user's operational permissions match the requested device data.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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