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-mw6p-33vw-46cchigh8.5

MantisBT: SQL Injection via history_order Configuration Value

Check your stack

The advisory, in context

MantisBT 2.28.3 and earlier versions contains a SQL injection vulnerability in core/history_api.php. The history_order configuration value is concatenated directly into a SQL ORDER BY clause without any sanitisation, parameterization, or validation against a whitelist.

An administrator can set this configuration value via the web UI (adm_config_set.php) or the REST API (PATCH /api/rest/config). The injected SQL then executes whenever any user views a bug with history entries.

Impact

  • Sensitive data extraction from the entire bugtracker database including user credentials (cookie_string, password hashes), API tokens, and private issue data
  • With MySQL FILE privilege: full RCE via INTO OUTFILE writing a PHP webshell to the web root
  • The admin plants the payload once; any authenticated user viewing a bug with history triggers the injection

Patches

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Resources

Credits

McCaulay Hudson (@McCaulay) of watchTowr

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 before 2.28.4

Fixed in 2.28.4

78 explicitly affected versions

2.10.0, 2.10.1, 2.11.0, 2.11.1, 2.12.0, 2.12.1, 2.12.2, 2.13.0, 2.13.1, 2.13.2, 2.14.0, 2.15.0, 2.15.1, 2.16.0, 2.16.1, 2.17.0, 2.17.1, 2.17.2, 2.18.0, 2.18.1, 2.19.0, 2.19.1, 2.20.0, 2.20.1, 2.21.0, 2.21.1, 2.21.2, 2.21.3, 2.22.0, 2.22.1, 2.22.2, 2.23.0, 2.23.1, 2.24.0, 2.24.1, 2.24.2, 2.24.3, 2.24.4, 2.24.5, 2.25.0, 2.25.1, 2.25.2, 2.25.3, 2.25.4, 2.25.5, 2.25.6, 2.25.7, 2.25.8, 2.26.0, 2.26.1, 2.26.2, 2.26.3, 2.26.4, 2.27.0, 2.27.1, 2.27.2, 2.27.3, 2.28.0, 2.28.1, 2.28.2, 2.28.3, 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.4.0, 2.4.1, 2.4.2, 2.5.0, 2.5.1, 2.5.2, 2.6.0, 2.7.0, 2.7.1, 2.8.0, 2.8.1, 2.9.0, 2.9.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "2.28.4"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "2.10.0",
    "2.10.1",
    "2.11.0",
    "2.11.1",
    "2.12.0",
    "2.12.1",
    "2.12.2",
    "2.13.0",
    "2.13.1",
    "2.13.2",
    "2.14.0",
    "2.15.0",
    "2.15.1",
    "2.16.0",
    "2.16.1",
    "2.17.0",
    "2.17.1",
    "2.17.2",
    "2.18.0",
    "2.18.1",
    "2.19.0",
    "2.19.1",
    "2.20.0",
    "2.20.1",
    "2.21.0",
    "2.21.1",
    "2.21.2",
    "2.21.3",
    "2.22.0",
    "2.22.1",
    "2.22.2",
    "2.23.0",
    "2.23.1",
    "2.24.0",
    "2.24.1",
    "2.24.2",
    "2.24.3",
    "2.24.4",
    "2.24.5",
    "2.25.0",
    "2.25.1",
    "2.25.2",
    "2.25.3",
    "2.25.4",
    "2.25.5",
    "2.25.6",
    "2.25.7",
    "2.25.8",
    "2.26.0",
    "2.26.1",
    "2.26.2",
    "2.26.3",
    "2.26.4",
    "2.27.0",
    "2.27.1",
    "2.27.2",
    "2.27.3",
    "2.28.0",
    "2.28.1",
    "2.28.2",
    "2.28.3",
    "2.3.0",
    "2.3.1",
    "2.3.2",
    "2.3.3",
    "2.4.0",
    "2.4.1",
    "2.4.2",
    "2.5.0",
    "2.5.1",
    "2.5.2",
    "2.6.0",
    "2.7.0",
    "2.7.1",
    "2.8.0",
    "2.8.1",
    "2.9.0",
    "2.9.1"
  ]
}

References