GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GHSA-36mj-6r7r-mqhfhigh

User can obtain JWT token even if account is disabled

No CVE assignedCheck your stack

The advisory, in context

Users can authenticate this way even if their user account is disabled. This is a high risk vulnerability when account disabling is used to block users' access to the system. (Someone who never had an account cannot exploit this vulnerability.) The fix ensures tokens are generated only for enabled user accounts, and is distributed via Composer as ezsystems/ezplatform-rest v1.3.8

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Ecosystem versions

From 1.3.0 before 1.3.8

Fixed in 1.3.8

9 explicitly affected versions

v1.3.0, v1.3.1, v1.3.1.1, v1.3.2, v1.3.3, v1.3.4, v1.3.5, v1.3.6, v1.3.7

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "1.3.0"
        },
        {
          "fixed": "1.3.8"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v1.3.0",
    "v1.3.1",
    "v1.3.1.1",
    "v1.3.2",
    "v1.3.3",
    "v1.3.4",
    "v1.3.5",
    "v1.3.6",
    "v1.3.7"
  ]
}

References