CVE-2025-65844

In EverShop, the customer update route is declared as public, causing the admin authentication middleware to call next() without checking the caller, and no customer-session middleware guards the route. An unauthenticated request with a known customer uuid can overwrite the customer's email and password, taking over the account. Version 2.2.1 changes the route to private.

EverShop 1.2.2 before 2.2.1 contains a missing authorization vulnerability in the customer address API that allows unauthenticated attackers to manage other customers' addresses. Attackers who know customer and address UUIDs can send POST, PATCH, or DELETE requests to /api/customers/:customer_id/addresses routes to add, modify, or delete saved shipping addresses.

A Blind Server-Side Request Forgery (SSRF) vulnerability in evershop 2.1.0 and prior allows unauthenticated attackers to force the server to initiate an HTTP request via the "GET /images" API. The vulnerability occurs due to insufficient validation of the "src" query parameter, which permits arbitrary HTTP or HTTPS URIs, resulting in unexpected requests against internal and external networks.

A DoS vulnerability in evershop 2.1.0 and prior allows unauthenticated attackers to exhaust application server resources via the "GET /images" API. The application fails to limit the height of the use-element shadow tree or the dimensions of pattern tiles during SVG processing, resulting in unbounded resource consumption and system-wide denial of service.

In EverShop up to 2.0.1, manipulation of the uuid argument in Order.resolvers.js of the Order Handler component results in improper control of resource identifiers. The attack can be performed remotely, is of high complexity and difficult exploitability, and the exploit is public.