# CVE-2026-3318: Multiple vulnerabilities in Cradle e-commerce

> Attackers can redirect users from the Cradle e-commerce login page to malicious external sites via an unvalidated returnUrl parameter.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-m29c-gmm3-c3v9

## What is CVE-2026-3318?

CVE-2026-3318 is a medium-severity vulnerability in Cradle e-commerce, published on 8 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Open redirection vulnerability in the latest demo version of the Cradle eCommerce platform. The vulnerability occurs in the login form endpoint, where the ‘returnUrl’ parameter allows redirection because the web application accepts a URL as a parameter without properly validating it. As a result, it is possible to redirect users from the legitimate website to external pages. An attacker could exploit this vulnerability to deceive users and redirect them from a trusted URL to a malicious one without their knowledge.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-3318?


## How do I fix CVE-2026-3318?

No fix has been published for CVE-2026-3318 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-3318 being exploited?

There is no known exploitation of CVE-2026-3318 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3318 and fix it if it is affected.

What it is: CVE-2026-3318 is a medium-severity vulnerability in Cradle e-commerce, published on 8 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-3318 in the wild and no public exploit code.

Affected product: Cradle e-commerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3318/ (Markdown: https://insights.sbomify.com/CVE-2026-3318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3318
- OSV: https://osv.dev/vulnerability/CVE-2026-3318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3318/
Summaries are generated and may contain mistakes; the official description above is the record.