CyberSecBulletin

EverShop vulnerabilities

We track 5 vulnerabilities in EverShop products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on January 5, 2026.

5vulnerabilities
1critical
4high
0exploited
8.0average CVSS score

Latest EverShop vulnerabilities

  • 7.5 High severity

    Evershop: Excessive Platform Resource Consumption within a Loop

    CVE-2025-67419EverShop

    A Denial of Service (DoS) vulnerability in evershop 2.1.0 and prior allows unauthenticated attackers to exhaust the application server's resources via the "GET /images" API. The application fails to limit the height of the use-element shadow tree or the dimens

  • 7.5 High severity

    Evershop: Unrestricted Upload of File with Dangerous Type

    CVE-2025-65844EverShop

    EverShop 2.0.1 allows a remote unauthenticated attacker to upload arbitrary files and create directories via the /api/images endpoint. The endpoint is accessible without authentication by default, and server-side validation of uploaded files is insufficient. T

  • 9.1 Critical severity

    Evershop: Use of Hard-coded Credentials

    CVE-2023-46943EverShop

    An issue was discovered in NPM's package @evershop/evershop before version 1.0.0-rc.8. The HMAC secret used for generating tokens is hardcoded as "secret". A weak HMAC secret poses a risk because attackers can use the predictable secret to create valid JSON We

  • 7.5 High severity

    Evershop: Improper Authentication

    CVE-2023-46942EverShop

    Lack of authentication in NPM's package @evershop/evershop before version 1.0.0-rc.8, allows remote attackers to obtain sensitive information via improper authorization in GraphQL endpoints.

  • 8.3 High severity

    Evershop: Improper Limitation of a Pathname to a Restricted Directory

    CVE-2023-46496EverShopEPSS 1.19%

    Directory Traversal vulnerability in EverShop NPM versions before v.1.0.0-rc.8 allows a remote attacker to obtain sensitive information via a crafted request to the DELETE function in api/files endpoint.