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

cve.new
Check your stack
GHSA-9m6v-8fxc-4r44low2.3No CVE assigned

Sulu: Used API Keys may be available via Admin API

Impact

The users endpoint controller exposes a project's apiKey field to the logged-in user, provided they have permission for that endpoint. This only has impact if a project itself uses that specific field, Sulu itself does nothing with it and has no authentication per apiKey in its core.

Source excerpt · OSV

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.

sulu/sulu Packagist
Affected rangeRecorded fix
From 3.0.0-alpha1 before 3.0.6Ecosystem versions3.0.6
Earlier releases before 2.6.23Ecosystem versions2.6.23

Version evidence: OSV · GHSA-9m6v-8fxc-4r44

View original version evidence (381 explicit versions)

Original source description

Impact

The users endpoint controller exposes a project's apiKey field to the logged-in user, provided they have permission for that endpoint. This only has impact if a project itself uses that specific field, Sulu itself does nothing with it and has no authentication per apiKey in its core.

Patches

A patch is released with Version 2.6.23 and 3.0.5.

Workarounds

Remove the field descriptor by patch the UserController.php File in Sulu Security Bundle.

References