Summary
EverShop's customer update route is publicly accessible without verifying that the requester is authenticated or owns the targeted customer record. An unauthenticated attacker who knows a customer UUID may change the customer's email address or password, potentially taking over the account.
Affected context
The vulnerability occurs in EverShop deployments where the customer update endpoint is configured as public and is not protected by customer-session or equivalent authorization middleware. It becomes risky when customer UUIDs are exposed through order confirmation links, administrative URLs, logs, or other observable application data, and the update handler trusts the path identifier without checking record ownership.
Exploit preconditions
- Attack surface: Customer update API route - Required access: No authenticated account is required if a valid customer
UUID is available
- Trigger point: Processing an update request for the customer identified
by the URL path
- Why exploitation is possible: Public route access bypasses administrator
authentication checks, while the handler lacks customer ownership
authorization before writing supplied fields
Why this happens
The route's access configuration allows requests to reach the update handler without authentication, and the middleware chain does not establish or verify the identity of the customer being modified. The handler treats a caller-controlled resource identifier as sufficient authority to update the corresponding record. This is a missing authorization flaw mapped to CWE-862, in which an application performs a sensitive action without enforcing the required permission check.
Potential impact
- An attacker may change a customer's email address.
- An attacker may set a new customer password and take over the account.
- The legitimate account owner could be locked out.
- Sensitive updated customer data could be disclosed in the response.
- An attacker could use compromised accounts for fraudulent orders or further abuse.
General mitigation guidance
Mitigation generally focuses on enforcing authorization at the resource and operation level rather than relying on route visibility or identifier secrecy. Common defensive patterns include requiring authenticated customer sessions for self-service updates, verifying that the authenticated identity owns the targeted record, and applying separate elevated authorization for administrative changes. Sensitive fields such as email addresses and passwords can use dedicated workflows with reauthentication, confirmation, and additional verification. Access should default to private, customer identifiers should not be treated as capabilities, and update operations should run with the least privilege needed to modify records.
How teams detect issues like this
Detection can include static analysis and code review rules that flag public routes performing writes to customer or other user-owned records, handlers that use path identifiers without ownership checks, and middleware chains lacking authentication or authorization enforcement. Dynamic testing can verify that unauthenticated users and authenticated users targeting another account receive denial responses. API policy enforcement can require authentication and resource-level authorization for sensitive update methods, while audit logs can monitor unexpected changes to email addresses, passwords, and customer ownership attributes. Automated security review tools may help identify missing authorization patterns during development.

