CVE-2025-55038
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 · uneditedAn authorization bypass vulnerability has been discovered in the Click Plus C2-03CPU2 device firmware version 3.60. Through the KOPR protocol utilized by the Remote PLC application, authenticated users with low-level access permissions can exploit this vulnerability to read and modify PLC variables beyond their intended authorization level.
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 confidenceThe Click Plus C2-03CPU2 PLC firmware 3.60 contains an authorization bypass in the KOPR protocol used by Remote PLC. Authenticated users with low-level access can read and modify PLC variables outside their authorized scope, effectively elevating their privileges to access restricted control system 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
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the PLC modelAccess the PLC programming software or web interface and verify the model is Click Plus C2-03CPU2Affected if The hardware model is not Click Plus C2-03CPU2 then this CVE does not apply
-
Check the firmware versionConnect to the PLC via the programming software or web interface and navigate to the firmware information section to determine the installed version numberAffected if The firmware version is exactly 3.60 then the device is affected
-
Verify Remote PLC interface is enabledCheck the PLC configuration settings for Remote PLC or KOPR protocol settings and confirm the interface is activeAffected if Remote PLC interface is enabled and firmware is 3.60 then the vulnerability is present
-
Review user accounts and access levelsAccess the user management or access control configuration panel and list all defined users with their permission levelsAffected if There are users configured with low-level or restricted access permissions then they could potentially exploit this flaw
-
Inspect variable access controlsExamine the PLC project configuration for variable access permissions and scope restrictions applied to user groupsAffected if Variable access controls exist but can be bypassed or are improperly scoped then the authorization flaw is exploitable
A user is affected if they operate a Click Plus C2-03CPU2 PLC with firmware version 3.60 that has Remote PLC interface enabled and contains users with restricted access levels.
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 dataApply vendor firmware update when available; until then, restrict network access to Remote PLC interface, enforce least-privilege access controls, and monitor for unauthorized variable access attempts.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55038 — 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-2025-55038 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