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-48f2-m7jg-866xlow3.7

Failed payment recorded has completed in Silverstripe Omnipay

Check your stack

The advisory, in context

Impact

For a subset of Omnipay gateways (those that use intermediary states like isNotification() or isRedirect()), if the payment identifier or success URL is exposed it is possible for payments to be prematurely marked as completed without payment being taken. This is mitigated by the fact that most payment gateways hide this information from users, however some issuing banks offer flawed 3DSecure implementations that may inadvertently expose this data.

Patches

The following versions have been patched to fix this issue:

  • 2.5.2
  • 3.0.2
  • 3.1.4
  • 3.2.1

Workarounds

There are no known workarounds for this vulnerability.

References

N/A.

For more information

If you have any questions or comments about this advisory:

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.5.2

Fixed in 2.5.2

15 explicitly affected versions

1.0.0, 1.0.0-beta1, 1.0.1, 1.0.2, 1.1.0, 1.1.1, 1.3.0, 2.0-alpha, 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0, 2.5.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "2.5.2"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "1.0.0",
    "1.0.0-beta1",
    "1.0.1",
    "1.0.2",
    "1.1.0",
    "1.1.1",
    "1.3.0",
    "2.0-alpha",
    "2.0.0",
    "2.1.0",
    "2.2.0",
    "2.3.0",
    "2.4.0",
    "2.5.0",
    "2.5.1"
  ]
}
Ecosystem versions

From 3.0.0 before 3.0.2

Fixed in 3.0.2

2 explicitly affected versions

3.0.0, 3.0.1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "3.0.0"
        },
        {
          "fixed": "3.0.2"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "3.0.0",
    "3.0.1"
  ]
}
Ecosystem versions

From 3.1.0 before 3.1.4

Fixed in 3.1.4

4 explicitly affected versions

3.1.0, 3.1.1, 3.1.2, 3.1.3

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "3.1.0"
        },
        {
          "fixed": "3.1.4"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "3.1.0",
    "3.1.1",
    "3.1.2",
    "3.1.3"
  ]
}
Ecosystem versions

From 3.2.0 before 3.2.1

Fixed in 3.2.1

1 explicitly affected versions

3.2.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "3.2.0"
        },
        {
          "fixed": "3.2.1"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "3.2.0"
  ]
}

References