Mageplaza GDPR for Magento up to 4.2.9 Address Delete Controller id ID missing authentication

Summaryinfo

A vulnerability, which was classified as critical, has been found in Mageplaza GDPR for Magento up to 4.2.9. Impacted is an unknown function of the file /customer/address/delete/id of the component Address Delete Controller. This manipulation of the argument ID causes missing authentication. This vulnerability is tracked as CVE-2026-79324. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Mageplaza GDPR for Magento up to 4.2.9. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /customer/address/delete/id of the component Address Delete Controller. The manipulation of the argument id with an unknown input leads to a missing authentication vulnerability. The CWE definition for the vulnerability is CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. As an impact it is known to affect integrity, and availability. The summary by CVE is:

Missing authorization in the Address Delete controller in Mageplaza GDPR for Magento 2 (mageplaza/module-gdpr) through 4.2.9 allows remote unauthenticated attackers to delete any customer's saved address, and to erase all stored addresses by iterating the address id, via a GET request to /customer/address/delete/id/{id}. The controller extends the legacy Action class instead of AbstractAccount, so no authentication, ownership or form key check is enforced.

The advisory is shared at packagist.org. This vulnerability is known as CVE-2026-79324 since 08/25/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/09/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• E-Commerce Management Software

Vendor

• Mageplaza

Name

• GDPR for Magento

Version

• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.2.9

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion