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
GHSA-xgr2-5837-hf48low3.7

NovoSGA: Manipulation of User Creation Page can lead to weak password requirements

Check your stack

The advisory, in context

A flaw has been found in Mangati NovoSGA up to 2.2.12. The impacted element is an unknown function of the file /novosga.users/new of the component User Creation Page. Executing manipulation of the argument Senha/Confirmação da senha can lead to weak password requirements. The attack can be launched remotely. Attacks of this nature are highly complex. The exploitability is regarded as difficult. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

Earlier releases through 2.2.12 (inclusive)

No fix recorded for this interval.

67 explicitly affected versions

2.0.0-RC1, 2.2.2, 2.2.3, v1.0.0, v1.0.1, v1.0.2, v1.0.3, v1.0.4, v1.1.0, v1.1.1, v1.1.2, v1.1.3, v1.1.4, v1.2.0, v1.2.1, v1.3.0, v1.3.1, v1.3.2, v1.3.3, v1.4.0, v1.4.1, v1.5.0, v1.5.1, v1.5.2, v2.0.0, v2.0.0-BETA1, v2.0.0-BETA2, v2.0.0-BETA3, v2.0.0-BETA4, v2.0.0-BETA5, v2.0.0-BETA6, v2.0.0-RC2, v2.0.0-RC3, v2.0.1, v2.0.10, v2.0.11, v2.0.2, v2.0.3, v2.0.4, v2.0.5, v2.0.6, v2.0.7, v2.0.8, v2.0.9, v2.1.0, v2.1.1, v2.1.2, v2.1.3, v2.1.4, v2.1.5, v2.1.6, v2.1.7, v2.1.8, v2.1.9, v2.2.0, v2.2.0-beta.1, v2.2.0-beta.2, v2.2.1, v2.2.10, v2.2.11, v2.2.12, v2.2.4, v2.2.5, v2.2.6, v2.2.7, v2.2.8, v2.2.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "last_affected": "2.2.12"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "2.0.0-RC1",
    "2.2.2",
    "2.2.3",
    "v1.0.0",
    "v1.0.1",
    "v1.0.2",
    "v1.0.3",
    "v1.0.4",
    "v1.1.0",
    "v1.1.1",
    "v1.1.2",
    "v1.1.3",
    "v1.1.4",
    "v1.2.0",
    "v1.2.1",
    "v1.3.0",
    "v1.3.1",
    "v1.3.2",
    "v1.3.3",
    "v1.4.0",
    "v1.4.1",
    "v1.5.0",
    "v1.5.1",
    "v1.5.2",
    "v2.0.0",
    "v2.0.0-BETA1",
    "v2.0.0-BETA2",
    "v2.0.0-BETA3",
    "v2.0.0-BETA4",
    "v2.0.0-BETA5",
    "v2.0.0-BETA6",
    "v2.0.0-RC2",
    "v2.0.0-RC3",
    "v2.0.1",
    "v2.0.10",
    "v2.0.11",
    "v2.0.2",
    "v2.0.3",
    "v2.0.4",
    "v2.0.5",
    "v2.0.6",
    "v2.0.7",
    "v2.0.8",
    "v2.0.9",
    "v2.1.0",
    "v2.1.1",
    "v2.1.2",
    "v2.1.3",
    "v2.1.4",
    "v2.1.5",
    "v2.1.6",
    "v2.1.7",
    "v2.1.8",
    "v2.1.9",
    "v2.2.0",
    "v2.2.0-beta.1",
    "v2.2.0-beta.2",
    "v2.2.1",
    "v2.2.10",
    "v2.2.11",
    "v2.2.12",
    "v2.2.4",
    "v2.2.5",
    "v2.2.6",
    "v2.2.7",
    "v2.2.8",
    "v2.2.9"
  ]
}

References