CyberSecBulletin
CVE-2025-41664NVD status: Deferred

Coupler 0750-0362: Incorrect Permission Assignment for Critical Resource

CVE-2025-41664 is a high-severity incorrect permission assignment for critical resource vulnerability in Coupler 0750-0362 from WAGO, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version FW13 as the first without the flaw, so updating Coupler 0750-0362 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.25% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Coupler 0750-0362 to FW13 or a later version.
  2. Update Coupler 0750-0362/0000-0001 to FW13 or a later version.
  3. Update Coupler 0750-0362/0040-0000 to FW13 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
WAGOCoupler 0750-0362before FW13FW13
WAGOCoupler 0750-0362/0000-0001before FW13FW13
WAGOCoupler 0750-0362/0040-0000before FW13FW13
WAGOCoupler 0750-0362/K013-1080before FW13FW13
WAGOCoupler 0750-0362/K019-7576before FW13FW13
WAGOCoupler 0750-0363before FW13FW13
WAGOCoupler 0750-0363/0040-0000before FW13FW13
WAGOCoupler 0750-0364/0040-0010before FW13FW13
WAGOCoupler 0750-0365/0040-0010before FW13FW13
WAGOCoupler 0750-0366before FW13FW13

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
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
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
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (cert.vde.com).

Official description

A low-privileged remote attacker could gain unauthorized access to critical resources, such as firmware and certificates, due to improper permission handling during the runtime of services (e.g., FTP/SFTP). This access could allow the attacker to escalate privileges and modify firmware.

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

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Incorrect Permission Assignment for Critical Resource vulnerabilities

Spotted an error? Tell us.