Productivity Suite: Incorrect Permission Assignment for Critical Resource
CVE-2025-62688 is a high-severity incorrect permission assignment for critical resource vulnerability in Productivity Suite from AutomationDirect, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Productivity Suite versions: SW V4.2.1.9 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.15% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Productivity 1000 P1-540 CPU to SW v4.4.1.19 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| AutomationDirect | Productivity Suite | SW V4.2.1.9 and earlier | Not stated |
| AutomationDirect | Productivity 3000 P3-622 CPU | SW V4.2.1.9 and earlier | Not stated |
| AutomationDirect | Productivity 3000 P3-550E CPU | SW V4.2.1.9 and earlier | Not stated |
| AutomationDirect | Productivity 3000 P3-530 CPU | SW v4.4.1.19 and earlier | Not stated |
| AutomationDirect | Productivity 2000 P2-622 CPU | SW v4.4.1.19 and earlier | Not stated |
| AutomationDirect | Productivity 2000 P2-550 CPU | SW v4.4.1.19 and earlier | Not stated |
| AutomationDirect | Productivity 1000 P1-550 CPU | SW v4.4.1.19 and earlier | Not stated |
| AutomationDirect | Productivity 1000 P1-540 CPU | before SW v4.4.1.19 | SW v4.4.1.19 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. Scored by CNA (hq.dhs.gov).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 6.9 | Medium | CNA (hq.dhs.gov) |
| CVSS 3.1 | 7.1 | High | CNA (hq.dhs.gov) |
Official description
An incorrect permission assignment for a critical resource vulnerability was discovered in Productivity Suite software version 4.4.1.19. The vulnerability allows an attacker with low-privileged credentials to change their role, gaining full control access to the project.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Productivity Suite
- 7.0 High severity
- 7.0 High severity
- 7.5 High severity
- 8.8 High severity
- 7.0 High severity
- 10.0 Critical severity
Recent Incorrect Permission Assignment for Critical Resource vulnerabilities
- 10.0 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.1 High severity
Spotted an error? Tell us.