CVE-2026-35063
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 · uneditedOpenPLC_V3 REST API endpoint checks for JWT presence but never verifies the caller's role. Any authenticated user with role=user can delete any other user, including administrators, by specifying their user ID or they can create new accounts with role=admin, escalating to full administrator access.
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 confidenceOpenPLC_V3 REST API authenticates users via JWT but fails to verify role authorization for sensitive operations. Any authenticated user with basic user role can delete any user (including administrators) or create new administrative accounts by manipulating user ID or role parameters in API requests, achieving full privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 OpenPLC V3 installationLocate the OpenPLC V3 web interface or service. Check common ports (8080, 8443) or search for 'openplc' processes. Inspect running services or containers for OpenPLC V3.Affected if OpenPLC V3 firmware is installed and running in the environment
-
Confirm REST API is accessibleAccess the REST API endpoint (typically at /api or /rest API base path). Verify the API responds to requests and requires JWT authentication.Affected if The REST API is exposed and uses JWT-based authentication
-
Test user deletion authorizationUsing a basic user account (non-admin), attempt to delete another user via the API (e.g., DELETE /api/users/{id}). Observe whether the request succeeds without proper admin role verification.Affected if A basic authenticated user can delete any user account including administrators
-
Test role manipulation during account creationUsing a basic user account, attempt to create a new user with elevated role privileges (admin role) via the API (e.g., POST /api/users with role=admin). Observe if the request succeeds.Affected if A basic user can create administrative accounts by manipulating role parameters
-
Verify authorization checks on sensitive endpointsReview API endpoint handlers or source code for role validation. Check if sensitive operations (user deletion, role modification) include authorization logic that verifies admin privileges before execution.Affected if Sensitive API endpoints lack role-based authorization validation
A user is affected if OpenPLC V3 is running and basic authenticated users can perform administrative actions without proper role authorization enforcement.
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 role-based access control (RBAC) checks on all sensitive API endpoints. Verify that the caller has admin privileges before allowing user deletion or account creation with elevated roles.
- 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-35063 — 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-35063 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