Skip to content

← Public intelligence

npm package

erxes

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.7npmAmendedPublished

    Erxes Incorrect Access Control vulnerability

    CVE-2024-57190 · GHSA-7rhv-xm4q-wh42

    Affected
    • npm erxes < 1.6.1
    Fixed in
    1.6.1· Vendor fix available
    Issue
    Erxes <1.6.1 is vulnerable to Incorrect Access Control. An attacker can bypass authentication by providing a "User" HTTP header that contains any user, allowing them to talk to any GraphQL endpoint.

    Recommended action: Upgrade to 1.6.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 7.7npmAmendedPublished

    Erxes Path Traversal vulnerability

    CVE-2024-57186 · GHSA-rq9r-qvwg-829q

    Affected
    • npm erxes < 1.6.2
    Fixed in
    1.6.2· Vendor fix available
    Issue
    In Erxes <1.6.2, an unauthenticated attacker can read arbitrary files from the system using a Path Traversal vulnerability in the /read-file endpoint handler.

    Recommended action: Upgrade to 1.6.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  3. Medium, CVSS 5.7npmAmendedPublished

    Erxes Path Traversal vulnerability

    CVE-2024-57189 · GHSA-2977-5php-6789

    Affected
    • npm erxes < 1.6.2
    Fixed in
    1.6.2· Vendor fix available
    Issue
    In Erxes <1.6.2, an authenticated attacker can write to arbitrary files on the system using a Path Traversal vulnerability in the importHistoriesCreate GraphQL mutation handler.

    Recommended action: Upgrade to 1.6.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →