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

