/

CVE-2026-79324

Severity:

HIGH RISK

(7.5)

Broken Access Control (CWE-639) in Mageplaza GDPR Module

CVE-2026-79324

Analyzed

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-639, CWE-862

Impact:

Unauthorized deletion of customer data

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A missing authorization check in the Mageplaza GDPR address-delete controller for Magento 2 allows unauthenticated remote attackers to delete saved customer addresses. Because the endpoint does not verify authentication, ownership, or a form key, an attacker may remove individual addresses or erase many addresses by targeting their identifiers.

Affected context

The vulnerability affects Magento 2 installations using the Mageplaza GDPR module through the affected release range. It occurs in the customer address deletion controller when requests reach an action that uses the legacy authorization model rather than the account-specific controller protections, leaving address ownership and request authenticity unchecked.

Exploit preconditions

  • Attack surface: Internet-accessible customer address deletion endpoint
  • Required access: No authentication is required
  • Trigger point: A GET request handled by the address-delete controller
  • Why exploitation is possible: The controller does not enforce customer authentication, address ownership, or form key validation, allowing attacker-supplied address identifiers to select deletion targets

Why this happens

The underlying flaw is a missing authorization decision at a state-changing controller action. The controller inherits from a legacy action class instead of an account-scoped controller, so framework protections for authenticated customer context and ownership are not applied. This maps primarily to CWE-639: Authorization Bypass Through User-Controlled Key, with CWE-862: Missing Authorization also applicable because the operation lacks an effective access-control check.

Potential impact

  • Unauthorized deletion of individual customers' saved addresses
  • Bulk removal of stored addresses by repeatedly targeting identifiers
  • Loss of customer convenience data and shipping information
  • Disruption of checkout and account-management workflows
  • Potential privacy or integrity concerns if address records are relied on operationally

General mitigation guidance

Mitigation generally focuses on making authorization explicit for every customer-owned resource operation.

Common defensive patterns include:

  • Restricting address deletion to authenticated customer sessions
  • Verifying that the requested address belongs to the current customer
  • Applying framework-supported account-controller authorization behavior
  • Requiring anti-CSRF protections for state-changing requests
  • Avoiding state-changing operations over unauthenticated GET requests
  • Returning consistent authorization failures without exposing resource existence
  • Applying least privilege to service identities that manage customer data

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis rules identifying state-changing routes without authorization checks
  • Code review signals such as legacy base controllers on customer-data actions
  • Tests that attempt cross-account access to object identifiers
  • Route-policy checks requiring authentication and CSRF protection for mutating operations
  • Web and application logs showing repeated address-deletion requests from unauthenticated clients
  • Automated security review tools that flag direct use of user-controlled identifiers without ownership validation

Sources

SourceLink
gist.github.comgist.github.com/mrtantoine/4311aa0c267c7a77c15d292820eb3c36
packagist.orgpackagist.org/packages/mageplaza/module-gdpr

Frequently asked

questions

Yes. The affected deletion action can be reached remotely, and the described weakness does not require the attacker to authenticate.

No valid customer account is required. The key condition is network access to the Magento endpoint and the ability to submit requests handled by the vulnerable controller.

Enforce authentication, verify resource ownership against the active customer context, and apply CSRF protections to the state-changing operation.

Use account-scoped controller patterns, require authorization checks for every object identifier, reject unsafe state changes over unauthenticated GET requests, and include cross-account authorization tests in CI and security reviews.

Find out what's already
exploitable in your codebase.